From: James Bottomley <James.Bottomley@steeleye.com>
To: Greg KH <greg@kroah.com>
Cc: 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, 04 Dec 2002 12:04:41 -0600 [thread overview]
Message-ID: <200212041804.gB4I4g803144@localhost.localdomain> (raw)
In-Reply-To: Message from Greg KH <greg@kroah.com> of "Wed, 04 Dec 2002 09:56:03 PST." <20021204175602.GC27780@kroah.com>
greg@kroah.com said:
> 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 problem is that the bus specific core registration no-longer knows if the
probes succeeded or failed (and if they did, what devices were attached),
since probing is controlled by the base core.
What the bus needs to know is when a driver attaches to a specific device (and
what device it has attached to).
Unless you have a better way of getting the attachment information out of the
bus after the base probes have executed, a notifier seemed to be the simplest
thing.
James
next prev parent reply other threads:[~2002-12-04 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 17:09 James Bottomley
2002-12-04 17:56 ` Greg KH
2002-12-04 18:04 ` James Bottomley [this message]
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
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=200212041804.gB4I4g803144@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.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
all inboxes | Powered by JetHome®