From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@linux.kernel.org
Subject: Re: PATCH: IDE generic tweak
Date: Wed, 13 Oct 2004 15:46:40 -0400 [thread overview]
Message-ID: <416D8620.5090001@pobox.com> (raw)
In-Reply-To: <1097679269.4696.18.camel@localhost.localdomain>
Alan Cox wrote:
> On Mer, 2004-10-13 at 16:49, Jeff Garzik wrote:
>
>>nVidia for example specifically wanted it because future __SATA__
>>hardware will appear at the legacy IDE addresses, and end users were
>>requesting for similar reasons.
>
>
> Guess we need a pair of options with similar names to specify who
> grabs the generic devices. That should be fine because it never wants
> to be automatic anyway
Can two drivers declare __setup() with the same string, I wonder?
Then you could do 'idegeneric=yes' and 'idegeneric=libata' or somesuch.
Jeff
prev parent reply other threads:[~2004-10-13 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 14:24 PATCH: IDE generic tweak Alan Cox
2004-10-13 15:31 ` Jeff Garzik
2004-10-13 14:39 ` Alan Cox
2004-10-13 15:49 ` Jeff Garzik
2004-10-13 14:54 ` Alan Cox
2004-10-13 19:46 ` Jeff Garzik [this message]
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=416D8620.5090001@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@linux.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).