mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: "Marco d'Itri" <md@linux.it>,
	linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: ide: MODALIAS support for autoloading of ide-cd, ide-disk, ...
Date: Tue, 6 Dec 2005 00:33:18 +0100	[thread overview]
Message-ID: <20051205233318.GB6554@vrfy.org> (raw)
In-Reply-To: <58cb370e0512051518j35885be1j44f7846e2d27c63d@mail.gmail.com>

On Tue, Dec 06, 2005 at 12:18:03AM +0100, Bartlomiej Zolnierkiewicz wrote:
> On 12/5/05, Marco d'Itri <md@linux.it> wrote:
> > On Dec 05, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> >
> > > Looks fine but what about ide-scsi driver and ide_optical media?
> > The Debian hotplug script, which does the same thing, does not know
> > about these modules and nobody ever complained, so if some support is
> 
> Does the hotplug script export kernel sysfs attributes?

You mean if the hotplug script uses sysfs? It looks up the
data in /proc (which is ugly, cause you have to loop until
the /proc file arrives).

> > needed it can be added later.
> 
> The problem is that you get wrong data for "modalias" sysfs attribute
> for ide-scsi module (because "modalias" is based on the media type).
> 
> Until this is issue solved I can't accept this patch.

The correct way is probably to have the same MODULE_ALIAS() in
ide-scsi and we just control the loaded module with the module-init-tools
blacklist entry. Does that make sense to you?

Thanks,
Kay

  reply	other threads:[~2005-12-05 23:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 17:24 Kay Sievers
2005-12-05  8:24 ` Bartlomiej Zolnierkiewicz
2005-12-05 18:28   ` Marco d'Itri
2005-12-05 23:18     ` Bartlomiej Zolnierkiewicz
2005-12-05 23:33       ` Kay Sievers [this message]
2005-12-05 23:36       ` Bartlomiej Zolnierkiewicz

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=20051205233318.GB6554@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=bzolnier@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md@linux.it \
    /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

all inboxes | Powered by JetHome®