From: Mark Rutland <mark.rutland@arm.com>
To: linux-kernel@vger.kernel.org, mingo@redhat.com
Cc: acme@redhat.com, apw@canonical.com, joe@perches.com,
mark.rutland@arm.com, paulmck@linux.vnet.ibm.com,
peterz@infradead.org
Subject: [PATCH 0/4] Final ACCESS_ONCE() cleanups for v4.15
Date: Mon, 27 Nov 2017 10:38:20 +0000 [thread overview]
Message-ID: <20171127103824.36526-1-mark.rutland@arm.com> (raw)
Now that the ACCESS_ONCE() conversion settled in v4.15-rc1, these
patches remove the ACCESS_ONCE() definitions from the kernel, along with
the newly redundant checkpatch warning suggesting {READ,WRITE}_ONCE()
are preferred.
One new user of ACCESS_ONCE() snuck into v4.15-rc1; the first patch in
this series (previously sent on its own [1]) moves that over to
READ_ONCE(). Otherwise, there are no remaining uses of ACCESS_ONCE().
Ingo, assuming there are no complaints, would you be happy to take this
via the tip tree as a fixup for v4.15?
I've also pushed the series to my core/access-once-removal branch [2].
Thanks,
Mark.
[1] https://lkml.kernel.org/r/20171114103138.9931-1-mark.rutland@arm.com
[2] git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git core/access-once-removal
Mark Rutland (4):
perf mmap: Convert ACCESS_ONCE() to READ_ONCE()
tools: include: remove ACCESS_ONCE()
compiler.h: remove ACCESS_ONCE()
checkpatch: remove ACCESS_ONCE() warning
include/linux/compiler.h | 47 ++++++++++--------------------------------
scripts/checkpatch.pl | 22 --------------------
tools/include/linux/compiler.h | 21 ++++++++-----------
tools/perf/util/mmap.h | 2 +-
4 files changed, 21 insertions(+), 71 deletions(-)
--
2.11.0
next reply other threads:[~2017-11-27 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 10:38 Mark Rutland [this message]
2017-11-27 10:38 ` [PATCH 1/4] perf mmap: Convert ACCESS_ONCE() to READ_ONCE() Mark Rutland
2017-12-12 15:06 ` [tip:locking/urgent] tools/perf: " tip-bot for Mark Rutland
2017-11-27 10:38 ` [PATCH 2/4] tools: include: remove ACCESS_ONCE() Mark Rutland
2017-12-12 15:07 ` [tip:locking/urgent] tools/include: Remove ACCESS_ONCE() tip-bot for Mark Rutland
2017-11-27 10:38 ` [PATCH 3/4] compiler.h: remove ACCESS_ONCE() Mark Rutland
2017-12-12 15:07 ` [tip:locking/urgent] compiler.h: Remove ACCESS_ONCE() tip-bot for Mark Rutland
2017-11-27 10:38 ` [PATCH 4/4] checkpatch: remove ACCESS_ONCE() warning Mark Rutland
2017-11-27 10:50 ` Joe Perches
2017-11-27 10:58 ` Mark Rutland
2017-12-12 15:07 ` [tip:locking/urgent] checkpatch: Remove " tip-bot for Mark Rutland
2017-11-27 21:11 ` [PATCH 0/4] Final ACCESS_ONCE() cleanups for v4.15 Paul E. McKenney
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=20171127103824.36526-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=acme@redhat.com \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®