From: Joe Perches <joe@perches.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Fengguang Wu <fengguang.wu@intel.com>,
ksummit-discuss <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [PATCH 13/13] rcutorture: formal: prepare for ACCESS_ONCE() removal
Date: Tue, 10 Oct 2017 09:57:25 -0700 [thread overview]
Message-ID: <1507654645.3552.37.camel@perches.com> (raw)
In-Reply-To: <20171010164139.GN27659@leverpostej>
On Tue, 2017-10-10 at 17:41 +0100, Mark Rutland wrote:
> On Tue, Oct 10, 2017 at 09:27:54AM -0700, Joe Perches wrote:
> > Once ACCESS_ONCE is removed from the code in the tree
> > it can also be removed from checkpatch
>
> Sure thing. We're expecting to rip that out with the ACCESS_ONCE
> definitions in a post-Coccinelle patch.
This treewide series is one of the types that would be nice to
have done at -rc1 via some external automated script service.
next prev parent reply other threads:[~2017-10-10 16:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 18:28 [PATCH 00/13] Preparatory work to kill off ACCESS_ONCE() Mark Rutland
2017-10-09 18:28 ` [PATCH 01/13] dm integrity: " Mark Rutland
2017-10-09 18:28 ` [PATCH 02/13] EDAC, altera: " Mark Rutland
2017-10-09 23:12 ` Thor Thayer
2017-10-10 9:30 ` Mark Rutland
2017-10-09 18:28 ` [PATCH 03/13] firmware/ivc: " Mark Rutland
2017-10-09 18:28 ` [PATCH 04/13] fs: dcache: " Mark Rutland
2017-10-09 18:28 ` [PATCH 05/13] fs: ncpfs: " Mark Rutland
2017-10-09 18:28 ` [PATCH 06/13] media: dvb_ringbuffer: " Mark Rutland
2017-10-09 18:28 ` [PATCH 07/13] net: netlink/netfilter: " Mark Rutland
2017-10-09 18:28 ` [PATCH 08/13] net/ipv4/tcp_input.c: " Mark Rutland
2017-10-09 19:03 ` Mark Rutland
2017-10-09 18:28 ` [PATCH 09/13] net: average: " Mark Rutland
2017-10-10 9:28 ` Mark Rutland
2017-10-09 18:28 ` [PATCH 10/13] samples: mic/mpssd/mpssd.c: " Mark Rutland
2017-10-09 18:28 ` [PATCH 11/13] selftests/powerpc: " Mark Rutland
2017-10-10 0:45 ` Michael Ellerman
2017-10-10 9:32 ` Mark Rutland
2017-10-09 18:28 ` [PATCH 12/13] workqueue: " Mark Rutland
2017-10-10 14:06 ` Tejun Heo
2017-10-10 16:21 ` Mark Rutland
2017-10-09 18:28 ` [PATCH 13/13] rcutorture: formal: prepare for ACCESS_ONCE() removal Mark Rutland
2017-10-09 19:51 ` Paul E. McKenney
2017-10-10 9:54 ` Mark Rutland
2017-10-10 12:47 ` Paul E. McKenney
2017-10-10 12:50 ` Mark Rutland
2017-10-10 14:52 ` Paul E. McKenney
2017-10-10 16:24 ` Mark Rutland
2017-10-10 16:35 ` Paul E. McKenney
2017-10-10 16:27 ` Joe Perches
2017-10-10 16:35 ` Paul E. McKenney
2017-10-10 16:41 ` Mark Rutland
2017-10-10 16:57 ` Joe Perches [this message]
2017-10-10 17:06 ` Mark Rutland
2017-10-09 20:02 ` [PATCH 00/13] Preparatory work to kill off ACCESS_ONCE() 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=1507654645.3552.37.camel@perches.com \
--to=joe@perches.com \
--cc=fengguang.wu@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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