From: Michael Tokarev <mjt@tls.msk.ru>
To: Greg K-H <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] PCI: add modalias sysfs file for pci devices
Date: Tue, 31 May 2005 20:50:07 +0400 [thread overview]
Message-ID: <429C95BF.3070102@tls.msk.ru> (raw)
In-Reply-To: <11163663063114@kroah.com>
Greg KH wrote:
> [PATCH] PCI: add modalias sysfs file for pci devices
[With similar patch and $MODALIAS in hotplug path stuff
submitted for USB]
Speaking of all this... While the two (USB and PCI) are
most important nowadays... Hmm, so probably all other
similar "busses", like PCMCIA, even bluetooth, and "not
so obvious ones" like IDE and SCSI, and PNP&EISA -- this
same approach may be used for all, providing device/modalias
file for all (scsi:t0 for sd_mod etc), and $MODALIAS for
hotpluggable ones, with appropriate .modalias in modules...
I mean, are we on the way to converting just everything
into this modalias thing, so that hotplug/modloading will
be just one-liner?
Providing "trivial" aliases for eg PNP or EISA busses
seems to be a bit redundrand (a list of pnp:dXXX in
device/modalias in addition to XXX in device/id), but
without that this whole picture will not be consistent...
or should it?
/mjt
next prev parent reply other threads:[~2005-05-31 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 21:44 [GIT PATCH] PCI bugfixes for 2.6.12-rc4 Greg KH
2005-05-17 21:45 ` [PATCH] PCI Hotplug: Fix echoing 1 to power file of enabled slot problem with SHPC driver Greg KH
2005-05-17 21:45 ` [PATCH] PCI Hotplug: CPCI update Greg KH
2005-05-17 21:45 ` [PATCH] PCI Hotplug: get pciehp to work on the downstream port of a switch Greg KH
2005-05-17 21:45 ` [PATCH] PCI Hotplug: remove pci_visit_dev Greg KH
2005-05-17 21:45 ` [PATCH] PCI: add modalias sysfs file for pci devices Greg KH
2005-05-17 21:45 ` [PATCH] PCI: add MODALIAS to hotplug event " Greg KH
2005-05-31 16:50 ` Michael Tokarev [this message]
2005-06-01 21:36 ` [PATCH] PCI: add modalias sysfs file " Greg KH
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=429C95BF.3070102@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--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