From: Christoph Hellwig <hch@infradead.org>
To: Markus Lidel <Markus.Lidel@shadowconnect.com>
Cc: Christoph Hellwig <hch@infradead.org>,
alan@lxorguk.ukuu.org.uk, wtogami@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: Merge I2O patches from -mm
Date: Thu, 19 Aug 2004 10:48:29 +0100 [thread overview]
Message-ID: <20040819104829.A7705@infradead.org> (raw)
In-Reply-To: <4123E73F.7040409@shadowconnect.com>; from Markus.Lidel@shadowconnect.com on Thu, Aug 19, 2004 at 01:33:19AM +0200
> > add a controller_add and add controller_remove method, taking a typesafe
> > i2o_controller * instead of the multiplexer.
>
> I had this before, but i want the notification also for I2O devices,
> because the driver model won't call probe functions for devices, which
> are already occupied by a other driver.
Then please add more methods. Multiplexer calls are an extremly bad idea.
> This is not the best solution,
> if you have more then one drivers which could handle a device. This is
> the case in e.g. i2o_proc, which only want to display information, and
> is not a "real driver". So finally there will be controller_add,
> controller_remove, device_add, device_remove... and i thought it would
> be more generic, and i also don't have to add a function each time a new
> notification is needed :-)
Yes, that's the whole point of this methods..
> Also i tried to implement the notification like the one already in the
> kernel, so i could exchange my notification facility with the already
> existing one (include/linux/notifier.h)...
linux/notifier.h is an bad example to follow and for many thing we're
moving slowly away from it (e.g. the shutdown notifications are now
exposed through the driver model)
next prev parent reply other threads:[~2004-08-19 9:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 23:08 Merge I2O patches from -mm Markus Lidel
2004-08-18 23:24 ` Christoph Hellwig
2004-08-18 23:33 ` Markus Lidel
2004-08-19 9:48 ` Christoph Hellwig [this message]
2004-08-19 10:16 ` Markus Lidel
2004-08-19 10:06 ` Christoph Hellwig
2004-08-19 11:54 ` Markus Lidel
2004-08-23 17:55 ` Christoph Hellwig
2004-08-24 8:16 ` Markus Lidel
2004-08-24 12:45 ` Christoph Hellwig
2004-08-24 16:00 ` Markus Lidel
2004-08-28 10:13 ` Warren Togami
-- strict thread matches above, loose matches on Subject: below --
2004-08-15 10:15 Warren Togami
2004-08-17 2:15 ` Andrew Morton
2004-08-17 8:36 ` Markus Lidel
2004-08-17 11:53 ` Christoph Hellwig
2004-08-17 13:31 ` Markus Lidel
2004-08-17 14:00 ` Alan Cox
2004-08-17 15:06 ` Christoph Hellwig
2004-08-17 14:50 ` Alan Cox
2004-08-17 15:17 ` Christoph Hellwig
2004-08-17 17:05 ` Markus Lidel
2004-08-17 16:56 ` Christoph Hellwig
2004-08-17 18:37 ` Markus Lidel
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=20040819104829.A7705@infradead.org \
--to=hch@infradead.org \
--cc=Markus.Lidel@shadowconnect.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wtogami@redhat.com \
/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