From: Ben Collins <bcollins@debian.org>
To: Greg KH <greg@kroah.com>
Cc: Patrick Mochel <mochel@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] Device removal callback
Date: Mon, 10 Mar 2003 13:12:51 -0500 [thread overview]
Message-ID: <20030310181251.GA1311@phunnypharm.org> (raw)
In-Reply-To: <20030310172155.GA9792@kroah.com>
It's less work to add all this overhead back into my subsystem than to
argue about it's worthiness. It seemed obviously in-line with the
driver-model's purpose to have a remove callback, but maybe my way of
thinking is expecting too much from the driver core, and I should do the
work myself in the subsystem.
thanks
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-03-10 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 18:14 [RFC] [PATCH] Device removal callback Ben Collins
2003-03-10 0:11 ` Greg KH
2003-03-10 1:02 ` Ben Collins
2003-03-10 15:59 ` Patrick Mochel
2003-03-10 16:55 ` Ben Collins
2003-03-10 17:21 ` Greg KH
2003-03-10 18:12 ` Ben Collins [this message]
2003-03-10 15:45 ` Patrick Mochel
2003-03-10 16:30 ` Ben Collins
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=20030310181251.GA1311@phunnypharm.org \
--to=bcollins@debian.org \
--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