From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
Grant Coady <gcoady.lk@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ATA Kconfig cleanup: hide ATA_SFF and add SATA/PATA menu items
Date: Sun, 17 Aug 2008 00:20:55 -0400 [thread overview]
Message-ID: <48A7A727.1030300@garzik.org> (raw)
In-Reply-To: <20080816113224.5562a9a6@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> I suspect sata_via will want this too.
>
> Lust about any PATA chip may be on boards with SATA bridges so the divide
> doesn't really work.
That's my reason for why the patches like this tend to be uninteresting...
Jeff
next prev parent reply other threads:[~2008-08-17 4:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 5:15 [PATCH 1/3] ATA Kconfig cleanup: hide ATA_SFF and add SATA/PATA menu items Grant Coady
2008-08-16 10:01 ` Mikael Pettersson
2008-08-16 10:32 ` Alan Cox
2008-08-17 4:20 ` Jeff Garzik [this message]
2008-08-18 1:47 ` [PATCH] ATA Kconfig cleanup: sort the driver list and modify some text Grant Coady
2008-08-18 8:56 ` Alan Cox
2008-08-20 23:27 ` Krzysztof Halasa
2008-08-21 0:16 ` Grant Coady
2008-08-21 0:49 ` Krzysztof Halasa
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=48A7A727.1030300@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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