public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: David Brownell <david-b@pacbell.net>
Cc: Greg KH <gregkh@suse.de>, Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.19-rc6] fix hotplug for legacy platform drivers
Date: Tue, 5 Dec 2006 11:01:52 +0100	[thread overview]
Message-ID: <20061205100152.GB5805@bongo.bofh.it> (raw)
In-Reply-To: <200612041828.01381.david-b@pacbell.net>

On Dec 05, David Brownell <david-b@pacbell.net> wrote:

> The pushback on $SUBJECT patch.  Which amounts to wanting to break hotplug
> for several busses, unless someone (NOT the folk promoting the breakage!)
Please explain in more details how hotplugging would be broken, possibly
with examples.

> There are really two issues here:
> 
>  - The "real one", as (yes!) fixed by the $SUBJECT patch.  Troublesome legacy
>    drivers, like "i82365", written so they can't hotplug ... but the kernel
>    hasn't previously known that.
> 
>  - The confusion, caused by a false identification of the "i82365" issue
>    being a problem related to module aliasing ... instead of being rooted in
>    the fact that it's a "legacy style" non-hotpluggable driver, since it
>    creates its own device node.

Nonsense. The purpose of $MODALIAS is to allow automatically loading
modules using the information provided by the bus driver.
Because of this reason there is no point for a driver to provide a
$MODALIAS referring to itself. It will only waste resources causing udev
to try loading it again.

-- 
ciao,
Marco

  reply	other threads:[~2006-12-05 10:01 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
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 [this message]
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=20061205100152.GB5805@bongo.bofh.it \
    --to=md@linux.it \
    --cc=david-b@pacbell.net \
    --cc=gregkh@suse.de \
    --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