From: Richard Kuo <rkuo@codeaurora.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: vapier@gentoo.org, eric.dumazet@gmail.com,
linux-kernel@vger.kernel.org, paulus@samba.org,
Anton Blanchard <anton@samba.org>,
linux-hexagon@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
asharma@fb.com
Subject: Re: [PATCH 1/2] atomic: Allow atomic_inc_not_zero to be overridden
Date: Thu, 1 Mar 2012 17:48:24 -0600 [thread overview]
Message-ID: <20120301234824.GC2644@codeaurora.org> (raw)
In-Reply-To: <20120301150256.9a7d0b06.akpm@linux-foundation.org>
On Thu, Mar 01, 2012 at 03:02:56PM -0800, Andrew Morton wrote:
> Please merge this via the ppc tree?
>
>
> And let's ask the hexagon maintainers to take a look at the definition
> in arch/hexagon/include/asm/atomic.h. I assume that it can be removed,
> but that might cause problems with files which include asm/atomic.h
> directly. I have found two such files in non-arch code and have queued
> fixes. There are no such files in arch/hexagon code, so I think it's
> safe to zap the hexagon definition of atomic_inc_not_zero().
Just tested it; it's safe to zap the Hexagon definition of
atomic_inc_not_zero()... I'm fine with this going in through some
other tree (still getting mine set up).
Thanks,
Richard Kuo
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2012-03-01 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 7:09 [PATCH 1/2] atomic: Allow atomic_inc_not_zero to be overridden Anton Blanchard
2012-03-01 7:12 ` [PATCH 2/2] powerpc: atomic: Implement atomic*_inc_not_zero Anton Blanchard
2012-03-01 17:19 ` [PATCH 1/2] atomic: Allow atomic_inc_not_zero to be overridden Mike Frysinger
2012-03-01 23:02 ` Andrew Morton
2012-03-01 23:48 ` Richard Kuo [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=20120301234824.GC2644@codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=asharma@fb.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=vapier@gentoo.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 NNTP newsgroup(s).