From: Ben Dooks <ben-linux@fluff.org>
To: Olof Johansson <olof@lixom.net>
Cc: linux-ide@vger.kernel.org, htejun@gmail.com, jeff@garzik.org,
Ben Dooks <ben-linux@fluff.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/3 2.6.24-git] PPC/LIBATA: Select HAVE_PATA_PLATFORM for ARCH_PPC
Date: Sat, 2 Feb 2008 19:41:02 +0000 [thread overview]
Message-ID: <20080202194102.GJ26792@trinity.fluff.org> (raw)
In-Reply-To: <20080202191239.GA29039@lixom.net>
On Sat, Feb 02, 2008 at 01:12:39PM -0600, Olof Johansson wrote:
> On Sat, Feb 02, 2008 at 04:21:36PM +0000, Ben Dooks wrote:
> > Use the new HAVE_PATA_PLATFORM to select PATA_PLATFORM
> > driver.
> >
> > CC: linuxppc-dev@ozlabs.org
> > Signed-off-by: Ben Dooks <ben-linux@fluff.org>
>
> What tree is this against? It doesn't apply to current mainline nor
> jgarzik's libata-dev upstream branch.
It is a series that i've just sent to the linux-ide list, only the ppc
part was cc'd to the ppc list.
> Anyway: NACK: I like this approach but this needs to be added to
> arch/powerpc as well.
I can add that to the series.
> It's actually more needed there than arch/ppc, I don't personally care
> if arch/ppc can't use pata_platform for the last couple of months it's
> still around (it's getting deleted this summer, all platforms should
> have moved to powerpc by then).
Thanks, didn't know that.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2008-02-02 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080202162133.678366209@fluff.org.uk>
2008-02-02 16:21 ` [PATCH 3/3 2.6.24-git] PPC/LIBATA: Select HAVE_PATA_PLATFORM for ARCH_PPC Ben Dooks
2008-02-02 19:12 ` Olof Johansson
2008-02-02 19:41 ` Ben Dooks [this message]
2008-02-03 0:23 ` Olof Johansson
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=20080202194102.GJ26792@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).