From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Neuling <michael.neuling@au1.ibm.com>
Cc: Linux PPC dev <linuxppc-dev@ozlabs.org>,
miltonm@realtime.net, Nishanth Aravamudan <nacc@us.ibm.com>
Subject: Re: [PATCH] powerpc: Add isync to copy_and_flush
Date: Thu, 25 Apr 2013 02:36:57 +1000 [thread overview]
Message-ID: <1366821417.2869.12.camel@pasglop> (raw)
In-Reply-To: <29244.1366799409@ale.ozlabs.ibm.com>
On Wed, 2013-04-24 at 20:30 +1000, Michael Neuling wrote:
> benh: we should get this in 3.9 ASAP.
Considering that the bug has been there *forever* I don't think I have a
real standing to try to shove it down Linus throat as a "regression
fix" :-)
I'll put the fix in 3.10 and let it trickle down to stable.
Cheers,
Ben.
next prev parent reply other threads:[~2013-04-24 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:30 [PATCH] powerpc: Add isync to copy_and_flush Michael Neuling
2013-04-24 16:36 ` Benjamin Herrenschmidt [this message]
2013-04-25 0:19 ` Michael Neuling
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=1366821417.2869.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael.neuling@au1.ibm.com \
--cc=miltonm@realtime.net \
--cc=nacc@us.ibm.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).