From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: [PATCH 3/8] Documentation/sparse: drop __bitwise__
Date: Thu, 15 Dec 2016 07:15:15 +0200 [thread overview]
Message-ID: <1481778865-27667-4-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1481778865-27667-1-git-send-email-mst@redhat.com>
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>
---
Documentation/dev-tools/sparse.rst | 7 -------
1 file changed, 7 deletions(-)
diff --git a/Documentation/dev-tools/sparse.rst b/Documentation/dev-tools/sparse.rst
index 8c250e8..e08e6a8 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
------------------------------
--
MST
next prev parent reply other threads:[~2016-12-15 5:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 5:15 [PATCH 0/8] enable endian checks for all sparse builds Michael S. Tsirkin
2016-12-15 5:15 ` [PATCH 1/8] linux/types.h: " Michael S. Tsirkin
2016-12-15 5:15 ` [PATCH 2/8] tools: " Michael S. Tsirkin
2016-12-15 5:15 ` Michael S. Tsirkin [this message]
2016-12-15 5:15 ` [PATCH 4/8] checkpatch: replace __bitwise__ with __bitwise Michael S. Tsirkin
2016-12-15 15:22 ` Joe Perches
2016-12-15 5:15 ` [PATCH 5/8] linux: drop __bitwise__ everywhere Michael S. Tsirkin
2016-12-15 9:04 ` Stefan Schmidt
2016-12-15 11:51 ` Greg Kroah-Hartman
2016-12-15 17:28 ` Krzysztof Kozlowski
2016-12-15 19:44 ` Lee Duncan
2016-12-19 9:09 ` Luca Coelho
2016-12-15 5:15 ` [PATCH 6/8] Documentation/sparse: drop __CHECK_ENDIAN__ Michael S. Tsirkin
2016-12-15 5:15 ` [PATCH 7/8] fs/logfs: " Michael S. Tsirkin
2016-12-15 5:15 ` [PATCH 8/8] Makefile: drop -D__CHECK_ENDIAN__ from cflags Michael S. Tsirkin
2016-12-15 7:00 ` Marcel Holtmann
2016-12-15 7:57 ` Marc Kleine-Budde
2016-12-15 11:50 ` Greg Kroah-Hartman
2016-12-15 20:15 ` Arend Van Spriel
2016-12-19 9:08 ` Luca Coelho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1481778865-27667-4-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox