From: Davidlohr Bueso <dave@stgolabs.net>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Shradha Shah <sshah@solarflare.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
William Hubbs <w.d.hubbs@gmail.com>,
Chris Brannon <chris@the-brannons.com>,
Kirk Reiser <kirk@reisers.ca>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Aybuke Ozdemir <aybuke.147@gmail.com>,
linux-net-drivers@solarflare.com, linux-doc@vger.kernel.org,
netdev@vger.kernel.org, speakup@linux-speakup.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH v2] atomics,cmpxchg: Privatize the inclusion of asm/cmpxchg.h
Date: Sun, 13 Sep 2015 15:47:40 -0700 [thread overview]
Message-ID: <20150913224740.GF19736@linux-q0g1.site> (raw)
In-Reply-To: <1441762024-2081-1-git-send-email-boqun.feng@gmail.com>
On Wed, 09 Sep 2015, Boqun Feng wrote:
>After commit:
>
>atomics: add acquire/release/relaxed variants of some atomic operations
>
>Architectures may only provide {cmp,}xchg_relaxed definitions in
>asm/cmpxchg.h. Other variants, such as {cmp,}xchg, may be built in
>linux/atomic.h, which means simply including asm/cmpxchg.h may not get
>the definitions of all the{cmp,}xchg variants. Therefore, we should
>privatize the inclusions of asm/cmpxchg.h to keep it only included in
>arch/* and replace the inclusions outside with linux/atomic.h
>
>Acked-by: Will Deacon <will.deacon@arm.com>
>Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
fwiw,
Acked-by: Davidlohr Bueso <dave@stgolabs.net>
prev parent reply other threads:[~2015-09-13 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 1:27 [PATCH v2] atomics,cmpxchg: Privatize the inclusion of asm/cmpxchg.h Boqun Feng
2015-09-09 4:00 ` Greg Kroah-Hartman
2015-09-13 22:47 ` Davidlohr Bueso [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=20150913224740.GF19736@linux-q0g1.site \
--to=dave@stgolabs.net \
--cc=aybuke.147@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=chris@the-brannons.com \
--cc=corbet@lwn.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=kishon@ti.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=sshah@solarflare.com \
--cc=w.d.hubbs@gmail.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).