From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@SteelEye.com>,
mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BKPATCH] bus notifiers for the generic device model
Date: Wed, 4 Dec 2002 10:52:25 -0800 [thread overview]
Message-ID: <20021204185225.GB28062@kroah.com> (raw)
In-Reply-To: <20021204181016.GB1584@beaverton.ibm.com>
On Wed, Dec 04, 2002 at 10:10:16AM -0800, Mike Anderson wrote:
> Greg KH [greg@kroah.com] wrote:
> > On Wed, Dec 04, 2002 at 11:09:21AM -0600, James Bottomley wrote:
> > > There are certain bus types (notably MCA and parisc internal ones) that like
> > > to do generic houskeeping operations (claim slots, claim uniform resources
> > > etc.) when drivers are attached to devices.
> >
> > But doesn't the bus specific core know when drivers are attached, as it
> > was told to register or unregister a specific driver? So I don't see
> > why this is really needed.
>
> The change is when a device is bound to a driver (i.e. when attach /
> detach is called bus.c ).
Whis is called after probe / remove is called for the driver, which can
point to the bus specific functions, like PCI and USB cores do.
thanks,
greg k-h
prev parent reply other threads:[~2002-12-04 18:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 17:09 [BKPATCH] bus notifiers for the generic device model James Bottomley
2002-12-04 17:56 ` Greg KH
2002-12-04 18:04 ` James Bottomley
2002-12-04 18:04 ` Patrick Mochel
2002-12-04 18:42 ` Jeff Garzik
2002-12-05 3:33 ` Patrick Mochel
2002-12-04 18:13 ` Greg KH
2002-12-04 19:35 ` James Bottomley
2002-12-04 22:29 ` Greg KH
2002-12-05 3:50 ` Patrick Mochel
2002-12-05 16:14 ` James Bottomley
2002-12-05 16:57 ` Jeff Garzik
2002-12-06 19:10 ` Patrick Mochel
2002-12-04 18:10 ` Mike Anderson
2002-12-04 18:52 ` Greg KH [this message]
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=20021204185225.GB28062@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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