Documentation/sparse: drop __bitwise__
We dropped __CHECK_ENDIAN__ so __bitwise__ is now an implementation detail. People should use __bitwise everywhere. Signed-off-by: Michael S. Tsirkin <mst@redhat.com>hifive-unleashed-5.1
parent
376a5fb34b
commit
9536099a8e
|
@ -51,13 +51,6 @@ sure that bitwise types don't get mixed up (little-endian vs big-endian
|
||||||
vs cpu-endian vs whatever), and there the constant "0" really _is_
|
vs cpu-endian vs whatever), and there the constant "0" really _is_
|
||||||
special.
|
special.
|
||||||
|
|
||||||
__bitwise__ - to be used for relatively compact stuff (gfp_t, etc.) that
|
|
||||||
is mostly warning-free and is supposed to stay that way. Warnings will
|
|
||||||
be generated without __CHECK_ENDIAN__.
|
|
||||||
|
|
||||||
__bitwise - noisy stuff; in particular, __le*/__be* are that. We really
|
|
||||||
don't want to drown in noise unless we'd explicitly asked for it.
|
|
||||||
|
|
||||||
Using sparse for lock checking
|
Using sparse for lock checking
|
||||||
------------------------------
|
------------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue