From: James Bottomley <James.Bottomley@steeleye.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Greg KH <greg@kroah.com>,
James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BKPATCH] bus notifiers for the generic device model
Date: Thu, 05 Dec 2002 10:14:30 -0600 [thread overview]
Message-ID: <200212051614.gB5GEUN02667@localhost.localdomain> (raw)
In-Reply-To: Message from Patrick Mochel <mochel@osdl.org> of "Wed, 04 Dec 2002 21:50:25 CST." <Pine.LNX.4.33.0212042135420.924-100000@localhost.localdomain>
mochel@osdl.org said:
> I don't see how your patch adresses chaining; there is only one
> notifier per bus type.
Well, you can do it by storing the pointer privately and hijacking it.
However, I think we'd use the existing kernel notifier chain stuff for that if
it is valuable.
> Along they way, we've found several things stand in the way of making
> this a smooth transition, so the plan is to stick with the bus
> intermediaries until the infrastructure matures enough to tackle
> those problems more easily.
I'm happy with keeping probe and remove in the bus specific driver template
and having the <bustype>_add_driver install generic device probe and remove
routines to handle these cases. My point was that the docs implied I should
use the generic driver probe and remove routines, which I can't without some
type of functionality like this.
If you envisage us never eliminating the driver specific probe and remove
routines, I'm happy. I'm less happy if there will come a day when I have to
revisit all the converted drivers to do the elimination.
James
next prev parent reply other threads:[~2002-12-05 16:07 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 [this message]
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=200212051614.gB5GEUN02667@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