From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Fix __flush_icache_range on 44x
Date: Tue, 18 Aug 2009 10:54:09 +1000 [thread overview]
Message-ID: <1250556849.4830.64.camel@pasglop> (raw)
In-Reply-To: <20090818001614.GG3095@hansolo.jdub.homelinux.org>
On Mon, 2009-08-17 at 20:16 -0400, Josh Boyer wrote:
>
> You can if you'd like. My biggest concern is getting time to
> recreate. I
> think I'll have time later in the week if you'd like to wait until
> then.
> I simply didn't want to send out a patch that I wasn't sure fixed the
> issue.
>
That's ok. It's a bug fix so it's less constrained by the upcoming merge
window and we can send it back to -stable later.
Cheers,
Ben.
next prev parent reply other threads:[~2009-08-18 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 13:41 [PATCH] powerpc: Fix __flush_icache_range on 44x Josh Boyer
2009-08-17 16:07 ` Josh Boyer
2009-08-17 21:46 ` Benjamin Herrenschmidt
2009-08-18 0:16 ` Josh Boyer
2009-08-18 0:54 ` Benjamin Herrenschmidt [this message]
2009-08-19 7:29 ` Benjamin Herrenschmidt
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=1250556849.4830.64.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).