From: Greg KH <gregkh@suse.de>
To: David Brownell <david-b@pacbell.net>
Cc: Kay Sievers <kay.sievers@vrfy.org>, "Marco d'Itri" <md@Linux.IT>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.19-rc6] fix hotplug for legacy platform drivers
Date: Wed, 29 Nov 2006 15:02:19 -0800 [thread overview]
Message-ID: <20061129230219.GA11539@suse.de> (raw)
In-Reply-To: <200611291450.59165.david-b@pacbell.net>
On Wed, Nov 29, 2006 at 02:50:58PM -0800, David Brownell wrote:
> On Monday 27 November 2006 11:03 am, Greg KH wrote:
>
> > David, any chance you can fix this up, as people are seeing this bug
> > today.
>
> Here's my fix. Unlike the fix Kay suggested, it causes at worst only
> a minor loss of functionality, so that tradeoff seems fair for a late
> merge. I audited all the drivers using the relevant APIs, and I can't
> see many (if any!) folk hitting problems from this.
But this still can cause the problem that your 'modalias' file in sysfs
contains exactly the same name as the module itself, right?
That's not good, it should be an alias, not the "real name".
I'd even settle for 'driver:MODULE_NAME' and have that automatically
generated by the driver core logic somehow (note, Kay came up with that
idea in the past, it's not new...)
So, I don't like this patch, can't we come up with a way for the alias
to be just that, an alias?
That will ensure that userspace tools do not get confused, _and_ it be
possible to properly use the 'blacklist' option to modprobe (which only
works on aliases right now, as it should.)
thanks,
greg k-h
next prev parent reply other threads:[~2006-11-29 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061122135948.GA7888@bongo.bofh.it>
[not found] ` <1164623293.3702.4.camel@pim.off.vrfy.org>
[not found] ` <20061127190315.GA28107@suse.de>
2006-11-29 22:50 ` [patch 2.6.19-rc6] fix hotplug for legacy platform drivers David Brownell
2006-11-29 23:02 ` Greg KH [this message]
2006-11-30 1:27 ` [Bulk] " David Brownell
2006-12-01 7:04 ` Greg KH
2006-12-05 2:28 ` David Brownell
2006-12-05 10:01 ` Marco d'Itri
2006-12-06 0:03 ` David Brownell
2006-12-06 6:08 ` Greg KH
2006-12-07 0:25 ` [Bulk] " David Brownell
2006-12-06 23:56 ` Marco d'Itri
2006-12-09 6:03 ` David Brownell
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=20061129230219.GA11539@suse.de \
--to=gregkh@suse.de \
--cc=david-b@pacbell.net \
--cc=kay.sievers@vrfy.org \
--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