From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Cloos <cloos@jhcloos.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: Schedule for adding pata to kernel?
Date: Thu, 30 Mar 2006 12:20:02 +0100 [thread overview]
Message-ID: <1143717602.29388.34.camel@localhost.localdomain> (raw)
In-Reply-To: <m3acb8eveg.fsf@lugabout.jhcloos.org>
On Mer, 2006-03-29 at 17:30 -0500, James Cloos wrote:
> My understanding is that with Alan's patch everything should be
> using major 8, and that CONFIG_IDE is no longer required, yes?
This is correct both if you are just using the existing SATA drivers or
if you are using the libata patch to drive older chips via libata.
You can mix and match but don't compile in two drivers for the same chip
Alan
next prev parent reply other threads:[~2006-03-30 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5SuEq-6ut-39@gated-at.bofh.it>
[not found] ` <5TDme-22E-27@gated-at.bofh.it>
[not found] ` <5UAcC-3bd-3@gated-at.bofh.it>
[not found] ` <5UH4o-4RJ-27@gated-at.bofh.it>
[not found] ` <5UTfA-5uK-17@gated-at.bofh.it>
2006-03-29 14:30 ` Schedule for adding pata to kernel? Robert Hancock
2006-03-29 14:36 ` Jeff Garzik
2006-03-29 22:30 ` James Cloos
2006-03-29 23:34 ` Robert Hancock
2006-03-31 5:37 ` James Cloos
2006-03-30 11:20 ` Alan Cox [this message]
2006-03-20 15:38 Libata PATA for 2.6.16 Alan Cox
2006-03-23 19:03 ` Chris Boot
2006-03-26 9:53 ` Schedule for adding pata to kernel? Harald Dunkel
2006-03-26 17:26 ` Alan Cox
2006-03-27 6:15 ` James Cloos
[not found] ` <b637ec0b0604180444y7828ac5aobb349324f87201c2@mail.gmail.com>
2006-04-18 12:00 ` Alan Cox
2006-04-18 12:13 ` Tejun Heo
2006-04-20 22:48 ` Jeff Garzik
2006-04-21 1:12 ` Tejun Heo
2006-04-21 6:38 ` Albert Lee
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=1143717602.29388.34.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cloos@jhcloos.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@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