From: Bjorn Helgaas <helgaas@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
llvm@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH v2 0/2] linux/types.h: Tidy __bitwise, add __CHECKER__ hints
Date: Tue, 15 Mar 2022 10:30:46 -0500 [thread overview]
Message-ID: <20220315153048.621328-1-helgaas@kernel.org> (raw)
From: Bjorn Helgaas <bhelgaas@google.com>
- Tidy up __bitwise__, which is unused except in the __bitwise definition
- Add hints about what __CHECKER__ means
Changes since v1:
- Also remove unnecessary __bitwise__ in tools/include/linux/types.h
(thanks to Andrew for pointing this out)
v1: https://lore.kernel.org/all/20220310220927.245704-1-helgaas@kernel.org/
Bjorn Helgaas (2):
linux/types.h: Remove unnecessary __bitwise__
Documentation/sparse: Add hints about __CHECKER__
Documentation/dev-tools/sparse.rst | 2 ++
include/linux/compiler_types.h | 1 +
include/uapi/linux/types.h | 6 +++---
tools/include/linux/types.h | 5 ++---
4 files changed, 8 insertions(+), 6 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-15 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 15:30 Bjorn Helgaas [this message]
2022-03-15 15:30 ` [PATCH v2 1/2] linux/types.h: Remove unnecessary __bitwise__ Bjorn Helgaas
2022-03-15 17:03 ` Michael S. Tsirkin
2022-05-25 6:51 ` Jiri Slaby
2022-05-25 14:34 ` Bjorn Helgaas
2022-03-15 15:30 ` [PATCH v2 2/2] Documentation/sparse: Add hints about __CHECKER__ Bjorn Helgaas
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=20220315153048.621328-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mst@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
/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