Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipc4: base_fw: Consistently use IPC4 status codes #9526

Commits on Sep 30, 2024

  1. ipc4: base_fw: Consistently use IPC4 status codes

    This patch addresses the issue of inconsistent error code usage in the
    base_fw.c file, where a mix of POSIX and IPC4 error codes was previously
    present.
    
    The IPC4 error codes are now used consistently throughout the file,
    ensuring that the error handling is aligned with the IPC4 protocol
    expectations. The changes include replacing POSIX error codes such as 0,
    -EINVAL, and -ENOMEM with their corresponding IPC4 status codes
    IPC4_SUCCESS, IPC4_ERROR_INVALID_PARAM, and IPC4_OUT_OF_MEMORY,
    respectively. This standardization helps to avoid confusion and
    potential bugs that can arise from the mixed usage of different error
    code conventions.
    
    Signed-off-by: Tomasz Leman <tomasz.m.leman@intel.com>
    tmleman committed Sep 30, 2024
    Configuration menu
    Copy the full SHA
    91f733a View commit details
    Browse the repository at this point in the history