linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@linux.intel.com>,
	linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH RFC] ata: Intel IDE-R support
Date: Wed, 18 Aug 2010 08:19:30 +0200	[thread overview]
Message-ID: <4C6B7B72.4090405@kernel.org> (raw)
In-Reply-To: <20100817192353.3529733c@lxorguk.ukuu.org.uk>

Hello,

On 08/17/2010 08:23 PM, Alan Cox wrote:
>> I don't really think it would be dangerous to grab intel IDE
>> controllers with ata_generic.  Again, that's what windows would do.
>> And for sysfs unbind case, if the user specifically unbinds the
>> controller from ata_piix, what is broken?
> 
> If the user changes the PCI id list what happens ?

Then that's upto the user, right?  That's what the (root) user wants.
You can add any random device ID to any random driver and if you do it
wrong something will break.  That's not different from any other
driver.

>> Maybe it's okay now but who's gonna remember what's going on there
>> after five years and nobody guarantees the above would continue to
> 
> Add a comment ?

Yeah, definitely.  Fat amount of them.

>> hold in the future.
> 
> It did occur to me to check this would be true in the future. Either way
> - an id table would go out of date more often.

Sure, the thing is that your patch doesn't mean we don't have to keep
ata_piix device table up-to-date.  We would still need to be
maintaining that table whether ata_generic can detect IDE-R by itself
or not.  The device ID table in ata_piix is given, and ata_generic
picking up the rest of intel IDE's wouldn't miss anything.  So, unless
IDE-R devices need some special treatment, I don't really see how the
detection code would be useful.

Thanks.

-- 
tejun

  reply	other threads:[~2010-08-18  6:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 15:56 [PATCH RFC] ata: Intel IDE-R support Alan Cox
2010-08-10 17:12 ` Sergei Shtylyov
2010-08-10 22:23   ` Alan Cox
2010-08-17 16:19 ` Tejun Heo
2010-08-17 16:42   ` Alan Cox
2010-08-17 16:30     ` Tejun Heo
2010-08-17 17:01       ` Alan Cox
2010-08-17 16:59         ` Tejun Heo
2010-08-17 18:23           ` Alan Cox
2010-08-18  6:19             ` Tejun Heo [this message]
2010-08-18 10:03               ` Alan Cox
2010-08-18 14:10                 ` Tejun Heo
2010-08-18 15:15                   ` Alan Cox
2010-08-19  9:37                     ` Tejun Heo
2010-08-19 10:09                       ` Alan Cox
2010-08-19 11:22                         ` Tejun Heo
2010-08-19 11:35                           ` Kay Sievers
2010-08-19 11:42                             ` Tejun Heo
2010-08-19 12:24                               ` Kay Sievers
2010-08-19 12:33                                 ` Tejun Heo
2010-08-19 12:52                                   ` Kay Sievers
2010-08-19 12:54                                     ` Tejun Heo
2010-08-19 13:08                                       ` Kay Sievers
2010-08-19 13:14                                         ` Tejun Heo
2010-08-19 12:56                           ` Tejun Heo
2010-08-19 18:05                             ` Jeff Garzik
2010-08-19 11:02                       ` Tim Small

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=4C6B7B72.4090405@kernel.org \
    --to=tj@kernel.org \
    --cc=alan@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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).