public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Dave Jones <davej@suse.de>, Paul Jakma <paulj@alphyra.ie>,
	knobi@knobisoft.de, linux-kernel@vger.kernel.org
Subject: Re: Hardware Inventory [was: Re: ISA slot detection on PCI systems?]
Date: Mon, 7 Jan 2002 11:29:03 -0800	[thread overview]
Message-ID: <20020107192903.GB8413@kroah.com> (raw)
In-Reply-To: <20020107185001.GK7378@kroah.com> <Pine.LNX.4.33.0201071109490.28000-100000@segfault.osdlab.org>
In-Reply-To: <Pine.LNX.4.33.0201071109490.28000-100000@segfault.osdlab.org>

On Mon, Jan 07, 2002 at 11:19:06AM -0800, Patrick Mochel wrote:
> 
> It's very closely related; kinda like kissing cousins.
> 
> /sbin/hotplug is called from the kernel only, right?

Right.  But there's no reason it can't be called from any other place.
It's just a userspace program with a well documented interface :)

> I see no reason to change that at all for notification of devices that are
> plugged in/removed by suprise.

Also realize that the first scan of a bus looks just like a device was
plugged in from the subsystem's point of view.

> I was thinking, though, more along the lines of triggering the probe for
> devices that the kernel has a tough time finding on its own. E.g. peer
> Host/PCI bridges, batteries, etc.

Ah, things that do not have individual kernel module drivers right now?

greg k-h

  reply	other threads:[~2002-01-07 19:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 11:32 Hardware Inventory [was: Re: ISA slot detection on PCI systems?] Martin Knoblauch
2002-01-04 22:17 ` Dave Jones
2002-01-05 17:00   ` Paul Jakma
2002-01-05 17:14     ` Dave Jones
2002-01-07 18:05       ` Patrick Mochel
2002-01-07 18:11         ` Dave Jones
2002-01-07 18:50           ` Greg KH
2002-01-07 18:58             ` Greg KH
2002-01-07 18:58               ` Eric S. Raymond
2002-01-08  8:04               ` [kbuild-devel] " Giacomo Catenazzi
2002-01-08 18:36                 ` Greg KH
2002-01-09  8:25                 ` Giacomo Catenazzi
2002-01-07 18:58             ` Dave Jones
2002-01-07 19:06               ` Greg KH
2002-01-07 19:19                 ` Dave Jones
2002-01-07 19:45                   ` Alexander Viro
2002-01-08 14:00                   ` Alan Cox
2002-01-08 14:00                     ` Erik Andersen
2002-01-07 19:19             ` Patrick Mochel
2002-01-07 19:29               ` Greg KH [this message]
2002-01-07 20:36                 ` David Brownell
2002-01-07 22:03                   ` Greg KH
2002-01-07 22:28                     ` David Brownell
2002-01-07 23:59                       ` Greg KH
2002-01-08  8:36                       ` Kevin Easton
2002-01-11 21:52                         ` David Brownell
2002-01-07 23:25       ` Kai Germaschewski
2002-01-07 17:55     ` Patrick Mochel
2002-01-07 19:04       ` Richard Gooch
2002-01-07 19:26         ` Dave Jones
2002-01-07 19:41           ` Alexander Viro
2002-01-07 19:58           ` Paul Jakma
2002-01-07 19:33         ` Patrick Mochel
2002-01-07 20:16           ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07 20:13 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=20020107192903.GB8413@kroah.com \
    --to=greg@kroah.com \
    --cc=davej@suse.de \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=paulj@alphyra.ie \
    /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