linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] ide_scsi: allow it to be used for non CD only
Date: Wed, 29 Nov 2006 23:47:04 +0100	[thread overview]
Message-ID: <58cb370e0611291447y36430d5bta65176eb1198cdce@mail.gmail.com> (raw)
In-Reply-To: <20061129223518.19f6ef95@localhost.localdomain>

On 11/29/06, Alan <alan@lxorguk.ukuu.org.uk> wrote:
> On Wed, 29 Nov 2006 23:05:56 +0100
> "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com> wrote:
>
> > Hi,
> >
> > Nowadays, you can dynamically change driver bound to a device using
> > sysfs and it works just fine for IDE, ie:
>
> This isn't the point of this change. The point is to do this at discovery
> time. If you do it later then many horrible things happen as the device

then "hdc=ide-cdrom" at a boot time should keep ide-scsi from
binding to hdc for all cases (builtin/modular ide-cd/ide-scsi)

> names and renames itself while udev goes boom.

Uh?  I hope that udev people are informed
about these horrible things...

/dev/hdc stays there all the time
/dev/sr? addition/removal should be handled
by udev otherwise it looks like a udev bug

> Its a small clean patch and it'll solve the problem nicely until
> drivers/ide dies.

No strong feelings here about the patch.  It is indeed a clean hack. ;)
I just wanted to point out that there are already more flexible ways
to achieve the same thing.

Bart

      reply	other threads:[~2006-11-29 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 14:46 [PATCH] ide_scsi: allow it to be used for non CD only Alan
2006-11-29 22:05 ` Bartlomiej Zolnierkiewicz
2006-11-29 22:35   ` Alan
2006-11-29 22:47     ` Bartlomiej Zolnierkiewicz [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=58cb370e0611291447y36430d5bta65176eb1198cdce@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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).