mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-kernel@vger.kernel.org
Cc: bjorn.helgaas@hp.com, ambx1@neo.rr.com, mm-commits@vger.kernel.org
Subject: Re: + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree
Date: Thu, 02 Mar 2006 17:55:47 -0700	[thread overview]
Message-ID: <m1veuwgxd8.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200603022340.k22Neq0o014875@shell0.pdx.osdl.net> (akpm@osdl.org's message of "Thu,  2 Mar 2006 15:43:07 -0800")

akpm@osdl.org writes:

> The patch titled
>
>      pnp: mpu401: adjust pnp_register_driver signature
>
> has been added to the -mm tree.  Its filename is
>
>      pnp-mpu401-adjust-pnp_register_driver-signature.patch
>
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> out what to do about this
>
>
> From: Bjorn Helgaas <bjorn.helgaas@hp.com>
>
> This series of patches removes the assumption that pnp_register_driver()
> returns the number of devices claimed.  Returning the count is unreliable
> because devices may be hot-plugged in the future.  (Many devices don't support
> hot-plug, of course, but PNP in general does.)

Huh?

How do onboard devices or ISA plug and play devices support hot-plug?

Or what devices supported by the pnp subsystem support hot-plug?

This may be a reasonable cleanup, but I'm worried about justifying it
with supporting hardware that does not exist.

Eric

       reply	other threads:[~2006-03-03  1:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603022340.k22Neq0o014875@shell0.pdx.osdl.net>
2006-03-03  0:55 ` Eric W. Biederman [this message]
2006-03-03  3:39   ` Bjorn Helgaas
2006-03-03  3:57     ` Eric W. Biederman
2006-03-03  6:58   ` Matthieu CASTET

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=m1veuwgxd8.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@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®