From: Kay Sievers <kay.sievers@vrfy.org>
To: Pierre Ossman <drzeus-mmc@drzeus.cx>
Cc: Andy Whitcroft <apw@canonical.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mmc: add MODALIAS linkage for MMC/SD devices
Date: Sun, 25 Jan 2009 00:45:46 +0100 [thread overview]
Message-ID: <ac3eb2510901241545l4eb9f77dvebd5861340b3447e@mail.gmail.com> (raw)
In-Reply-To: <20090124185612.5afddbb0@mjolnir.drzeus.cx>
On Sat, Jan 24, 2009 at 18:56, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> On Thu, 15 Jan 2009 15:00:03 +0000
> Andy Whitcroft <apw@canonical.com> wrote:
>
>>
>> Would it make more sense to simply use mmc: with no data as the MODALIAS
>> tag here. And make mmc-block have mmc:* as an alias. That way the
>> actual (useless) numeric data is not exposed but we still will load the
>> mmc-block module for everything exactly as we do with the udev rule.
>> This should still make things work from a distro point of view and not
>> expose anything which might then get relied on. If we do it so extra
>> data can still be added later we won't prevent sane data being exposed
>> should we ever have any.
>>
>> If you are happier with that I can re-spin the patches that way?
>>
>
> Well, as long as we're on the track of temporary hack, we might as well
> just export "mmc_block" as the modalias. Or would there be any
> side-effects to that?
The common format is to prefix with "<subsystem>:". Something like
"mmc:block" sounds fine to me.
Thanks,
Kay
next prev parent reply other threads:[~2009-01-24 23:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 18:56 Andy Whitcroft
2009-01-12 15:05 ` Pierre Ossman
2009-01-15 15:00 ` Andy Whitcroft
2009-01-24 17:56 ` Pierre Ossman
2009-01-24 23:45 ` Kay Sievers [this message]
2009-01-25 15:48 ` Pierre Ossman
2009-01-25 16:00 ` Kay Sievers
2009-01-26 9:35 ` Andy Whitcroft
2009-01-27 12:12 ` Andy Whitcroft
2009-01-27 19:14 ` Pierre Ossman
2009-01-27 19:26 ` Kay Sievers
2009-01-28 15:06 ` Andy Whitcroft
2009-01-28 19:58 ` Pierre Ossman
[not found] <20090218205654.05896ece@mjolnir.ossman.eu>
2009-02-23 12:38 ` Andy Whitcroft
2009-03-02 21:10 ` Pierre Ossman
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=ac3eb2510901241545l4eb9f77dvebd5861340b3447e@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=apw@canonical.com \
--cc=drzeus-mmc@drzeus.cx \
--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
all inboxes | Powered by JetHome®