aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/sparse.txt
diff options
context:
space:
mode:
authorSam Ravnborg <sam@ravnborg.org>2009-04-10 11:18:08 (GMT)
committerSam Ravnborg <sam@ravnborg.org>2009-04-11 06:18:11 (GMT)
commit20375bf82567b5fecd331048c6cc1fc292b67710 (patch)
tree1dc36f316f8e8d27d282f6cea6cf5adc97531b65 /Documentation/sparse.txt
parent5d7d18f5bc507b60d3d8967e2739d5e6ffdd630f (diff)
Documentation: explain the difference between __bitwise and __bitwise__
Simply added explanation from Al Viro in the following mail: http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/3164.html Cc: Al Viro <viro@ftp.linux.org.uk> Cc: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Diffstat (limited to 'Documentation/sparse.txt')
-rw-r--r--Documentation/sparse.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/sparse.txt b/Documentation/sparse.txt
index 42f43fa..34c76a5 100644
--- a/Documentation/sparse.txt
+++ b/Documentation/sparse.txt
@@ -42,6 +42,14 @@ 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.
+
+
Getting sparse
~~~~~~~~~~~~~~

Privacy Policy