diff options
author | Michael S. Tsirkin <mst@redhat.com> | 2016-12-11 06:28:41 +0200 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2016-12-16 00:13:40 +0200 |
commit | 9536099a8ef185abc0497d5e995ce23bd587a96e (patch) | |
tree | 253acc5a0a2d859b4ee38e622cd74c2c5eaa2a26 | |
parent | 376a5fb34b04524af501a0c5979c5920be940e05 (diff) |
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>
-rw-r--r-- | Documentation/dev-tools/sparse.rst | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/Documentation/dev-tools/sparse.rst b/Documentation/dev-tools/sparse.rst index 8c250e8a2105..e08e6a8effba 100644 --- a/Documentation/dev-tools/sparse.rst +++ b/Documentation/dev-tools/sparse.rst @@ -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_ 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 ------------------------------ |