From: Mark Rutland <mark.rutland@arm.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
ksummit-discuss <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH 13/13] rcutorture: formal: prepare for ACCESS_ONCE() removal
Date: Tue, 10 Oct 2017 18:06:52 +0100 [thread overview]
Message-ID: <20171010170652.GO27659@leverpostej> (raw)
In-Reply-To: <1507654645.3552.37.camel@perches.com>
On Tue, Oct 10, 2017 at 09:57:25AM -0700, Joe Perches wrote:
> 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.
Agreed, and this is exactly the plan.
As mentioned above, the treewide conversion is scripted with Coccinelle
(script below). The plan would be to regenerate this at an rc boundary,
once the preparatory patches (which cannot be scripted) have been
merged.
The ACCESS_ONCE() definitions and checkpatch bits would be removed in a
subsequent patch or series of patches.
Thanks,
Mark.
----
// Convert trivial ACCESS_ONCE() uses to equivalent READ_ONCE() and
// WRITE_ONCE()
virtual patch
@ depends on patch @
expression E1, E2;
@@
- ACCESS_ONCE(E1) = E2
+ WRITE_ONCE(E1, E2)
@ depends on patch @
expression E;
@@
- ACCESS_ONCE(E)
+ READ_ONCE(E)
----
prev parent reply other threads:[~2017-10-10 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1507573730-8083-1-git-send-email-mark.rutland@arm.com>
[not found] ` <1507573730-8083-14-git-send-email-mark.rutland@arm.com>
[not found] ` <20171009195112.GL3521@linux.vnet.ibm.com>
[not found] ` <20171010095413.GE27659@leverpostej>
[not found] ` <20171010124712.GV3521@linux.vnet.ibm.com>
[not found] ` <20171010125039.GI27659@leverpostej>
[not found] ` <20171010145252.GX3521@linux.vnet.ibm.com>
[not found] ` <1507652874.3552.34.camel@perches.com>
[not found] ` <20171010164139.GN27659@leverpostej>
2017-10-10 16:57 ` [Ksummit-discuss] [PATCH 13/13] rcutorture: formal: prepare for ACCESS_ONCE() removal Joe Perches
2017-10-10 17:06 ` Mark Rutland [this message]
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=20171010170652.GO27659@leverpostej \
--to=mark.rutland@arm.com \
--cc=joe@perches.com \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).