diff options
author | Damien Le Moal <[email protected]> | 2023-08-15 06:58:32 +0900 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2023-08-15 10:06:49 -0600 |
commit | c7b4b23b36edf32239e7fc3b922797ff1d32b072 (patch) | |
tree | cea2e72fe0ecd59f1b4b9ab270a812da4ecd13f9 /scripts/bpf_doc.py | |
parent | 649f070e69739d22c57c22dbce0788b72cd93fac (diff) |
block: uapi: Fix compilation errors using ioprio.h with C++
The use of the "class" argument name in the ioprio_value() inline
function in include/uapi/linux/ioprio.h confuses C++ compilers
resulting in compilation errors such as:
/usr/include/linux/ioprio.h:110:43: error: expected primary-expression before ‘int’
110 | static __always_inline __u16 ioprio_value(int class, int level, int hint)
| ^~~
for user C++ programs including linux/ioprio.h.
Avoid these errors by renaming the arguments of the ioprio_value()
function to prioclass, priolevel and priohint. For consistency, the
arguments of the IOPRIO_PRIO_VALUE() and IOPRIO_PRIO_VALUE_HINT() macros
are also renamed in the same manner.
Reported-by: Igor Pylypiv <[email protected]>
Fixes: 01584c1e2337 ("scsi: block: Improve ioprio value validity checks")
Signed-off-by: Damien Le Moal <[email protected]>
Reviewed-by: Chaitanya Kulkarni <[email protected]>
Tested-by: Igor Pylypiv <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Bart Van Assche <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'scripts/bpf_doc.py')
0 files changed, 0 insertions, 0 deletions