From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: sh:fixed issue in xchg_u32 function when val==r15.
Date: Wed, 08 Jun 2011 06:51:17 +0000 [thread overview]
Message-ID: <20110608065110.GA26006@linux-sh.org> (raw)
In-Reply-To: <4D9DB4A5.4010002@st.com>
On Tue, Apr 19, 2011 at 05:28:47PM +0100, Srinivas KANDAGATLA wrote:
> Attached is the reworked patch for potential gUSA rollback users.
>
Sorry for taking so long to get back to this, it's been in my review
queue for awhile now but other things kept getting in the way.
This looks good for the cmpxchg bits, but I suspect we also have to make
the same fixes for atomic-grb.h and bitops-grb.h.
I've applied your patch now and will send it off for -rc3. I expect
you'll simply send incremental patches for the other two if necessary,
after which we can make sure that it also all finds its way back to
-stable.
prev parent reply other threads:[~2011-06-08 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 12:57 sh:fixed issue in xchg_u32 function when val==r15 Srinivas KANDAGATLA
2011-04-07 16:53 ` Paul Mundt
2011-04-19 16:28 ` Srinivas KANDAGATLA
2011-06-08 6:51 ` Paul Mundt [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=20110608065110.GA26006@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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 NNTP newsgroup(s).