diff options
| author | Linus Torvalds <[email protected]> | 2022-05-25 16:02:19 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2022-05-25 17:08:59 +0000 |
| commit | caa28984163cb63ea0be4cb8dbf05defdc7303f9 (patch) | |
| tree | eef470377776f300b96cae38c5cb1883da0d0da4 /fs/jbd2/commit.c | |
| parent | media: lirc: revert removal of unused feature flags (diff) | |
| download | kernel-caa28984163cb63ea0be4cb8dbf05defdc7303f9.tar.gz kernel-caa28984163cb63ea0be4cb8dbf05defdc7303f9.zip | |
linux/types.h: reinstate "__bitwise__" macro for user space use
Commit c724c866bb70 ("linux/types.h: remove unnecessary __bitwise__")
was right that there are no users of __bitwise__ in the kernel, but it
turns out there are user space users of it that do expect it.
It is, after all, in the uapi directory, so user space usage is to be
expected.
Instead of reverting the commit completely, let's just clarify the
situation so that it doesn't happen again, and have some in-code
explanations for why that "__bitwise__" still exists.
Reported-by: Jiri Slaby <[email protected]>
Cc: Bjorn Helgaas <[email protected]>
Link: https://lore.kernel.org/all/[email protected]/
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions