From: Greg KH <greg@kroah.com>
To: Doug Maxey <dwm@austin.ibm.com>
Cc: Linux IDE Mailing List <linux-ide@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] IDE/ATA/SATA controller hotplug
Date: Sun, 25 Jul 2004 15:00:26 -0400 [thread overview]
Message-ID: <20040725190026.GA30535@kroah.com> (raw)
In-Reply-To: <200407191947.i6JJldK1024910@falcon10.austin.ibm.com>
On Mon, Jul 19, 2004 at 02:47:39PM -0500, Doug Maxey wrote:
>
> Howdy!
>
> This note went out originally to a semi-internal list, but after
> several comments, posting it here...
Unfortunatly, it seems you didn't listen to those comments :(
> What I would like is input on the general strategy that should be
> taken to modify the controller/adapter and device stack to:
>
> 1) be first class modules, where all controllers/adapters are
> capable of being loaded and unloaded. This is directed mostly at
> IDE/Southbridge controller/adapter devices.
>
> 2) extend that support to all child devices; disk, optical,
> and tape.
>
> 3) be part of mainline.
Great, that all sounds wonderful.
> The items I perceive at the top of the issue list are:
>
> - The primary platforms for IDE/ATA devices are x86 based, and
> certainly do not care about having this capability.
>
> - Assuming the capability is added, what rework would be acceptable
> for block devices?
Enough to make it work :)
> - Where should this capability go? Fork a subset of IDE
> controllers, and put them under the arch specific dir?
> Or include all devices?
Not in a arch specific dir please. You all do that too much as it is...
> - should we work to the goal of having the capability for all
> platforms, and all IDE devices?
Yes.
thanks,
greg k-h
next prev parent reply other threads:[~2004-07-25 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 19:47 [RFC] IDE/ATA/SATA controller hotplug Doug Maxey
2004-07-25 19:00 ` Greg KH [this message]
2004-07-26 19:42 ` Doug Maxey
2004-07-28 22:59 ` Greg KH
2004-07-27 15:31 ` Jeff Garzik
2004-07-27 20:18 ` Doug Maxey
2004-07-27 21:31 ` J. Ryan Earl
2004-07-27 20:47 ` Doug Maxey
2004-08-11 19:33 ` Jeff Garzik
2004-08-12 11:36 ` Paul Ionescu
2004-07-27 21:14 ` J. Ryan Earl
2004-07-27 20:15 ` Jeff Garzik
2004-07-27 20:20 ` Jeff Garzik
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=20040725190026.GA30535@kroah.com \
--to=greg@kroah.com \
--cc=dwm@austin.ibm.com \
--cc=linux-ide@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.