From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
Kay Sievers <kay.sievers@vrfy.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] [PNP] 'modalias' sysfs export
Date: Sat, 11 Mar 2006 20:07:24 +0300 [thread overview]
Message-ID: <200603112007.25589.arvidjaar@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Arjan van de Ven wrote:
> > On Sat, 2006-03-11 at 17:05 +0100, Pierre Ossman wrote:
> >> Here is a patch for doing multi line modalias for PNP devices. This will
> >> break udev, so that needs to be updated first.
> >
> > how could this EVER be acceptable???
>
> Soon I would hope. The modalias attribute currently only supports one
> alias (i.e. one line). This isn't enough for PNP, so if we want to
> support that bus (which I assume we do) we need to extend the interface.
> udev could be updated and be backwards compatible, the kernel can not
> (excluding adding another interface to the same data). So this patch
> should lag the update to udev a bit (i.e. I'm not suggesting it be
> applied now).
actually it is not that much udev but modprobe issue and modprobe already
supports multiple modules on command line (modprobe --all, module-init-tools
3.3.2 that I have here). So assuming module aliases cannot have embedded
spaces and udev properly space-splits command line (I have not checked, but
it should be the case IIRC) udev simply has to use 'modprobe --all $modalias'
to be compatible with this patch. It also remains backwards compatible with
single-alias modalias.
Or do I miss something obvious here? I understand that alternative is to make
every alias appear as separate device in sysfs, but I do not know PNP
structure well enough to decide if it makes sense.
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
iD8DBQFEEwPNR6LMutpd94wRAhpTAJ9DQ6gj4SM+6Arxqxb3hM5PA01cHACgjZQs
yrONSgp3+TAo1p2qzR1tAHg=
=eq0n
-----END PGP SIGNATURE-----
next reply other threads:[~2006-03-11 17:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 17:07 Andrey Borzenkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 21:40 [PATCH] [PNP] 'modalias' sysfs export Pierre Ossman
2006-03-01 19:45 ` Kay Sievers
2006-03-02 8:39 ` Pierre Ossman
2006-03-02 16:58 ` Kay Sievers
2006-03-03 11:52 ` Pierre Ossman
2006-03-11 16:05 ` Pierre Ossman
2006-03-11 16:15 ` Arjan van de Ven
2006-03-11 16:21 ` Pierre Ossman
2006-03-12 1:38 ` Andrew Morton
2006-03-12 4:05 ` Kay Sievers
2006-03-12 4:29 ` Adam Belay
2006-03-12 5:09 ` Kay Sievers
2006-03-12 6:01 ` Adam Belay
2006-03-12 11:17 ` Pierre Ossman
2006-03-12 11:33 ` Matthieu CASTET
2006-03-12 17:23 ` Kay Sievers
2006-03-12 22:55 ` Andrew Morton
2006-03-13 4:14 ` Kay Sievers
2006-03-13 6:02 ` Adam Belay
2006-03-13 6:21 ` Kay Sievers
2006-03-13 7:04 ` Adam Belay
2006-03-13 7:26 ` Adam Belay
2006-03-13 7:36 ` Kay Sievers
2006-03-14 1:25 ` Adam Belay
2006-03-13 16:57 ` Bill Nottingham
2006-03-13 19:24 ` Kay Sievers
2006-03-13 22:26 ` Bill Nottingham
2006-03-14 12:29 ` Sergey Vlasov
2006-03-14 12:47 ` Pierre Ossman
2006-03-14 15:00 ` Sergey Vlasov
2006-05-09 17:41 ` Pozsar Balazs
2006-05-12 11:09 ` Kay Sievers
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=200603112007.25589.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=arjan@infradead.org \
--cc=drzeus-list@drzeus.cx \
--cc=kay.sievers@vrfy.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