From: Greg KH <greg@kroah.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@home-tj.org>,
Patrick Mochel <mochel@digitalimplant.org>,
Adam Belay <ambx1@neo.rr.com>
Subject: Re: [RFC] [PATCH] driver core: allow userspace to unbind drivers from devices.
Date: Wed, 17 Nov 2004 09:55:05 -0800 [thread overview]
Message-ID: <20041117175504.GE28285@kroah.com> (raw)
In-Reply-To: <200411170200.32860.dtor_core@ameritech.net>
On Wed, Nov 17, 2004 at 02:00:32AM -0500, Dmitry Torokhov wrote:
> On Tuesday 16 November 2004 06:08 pm, Greg KH wrote:
> > On Tue, Nov 16, 2004 at 03:43:21PM -0500, Dmitry Torokhov wrote:
> > > On Mon, 15 Nov 2004 21:54:40 -0800, Greg KH <greg@kroah.com> wrote:
> > > > On Tue, Nov 09, 2004 at 10:49:43PM -0500, Dmitry Torokhov wrote:
> > > > > In the meantime, can I please have bind_mode patch applied? I believe
> > > > > it is useful regardless of which bind/unbind solution will be adopted
> > > > > and having them will allow me clean up serio bus implementaion quite a
> > > > > bit.
> > > > >
> > > > > Pretty please...
> > > >
> > > > Care to resend it? I can't find it in my archives.
> > > >
> > >
> > > Here it is, against 2.6.10-rc2. Apologies for sending it as an attachment
> > > but this interface will not let me put it inline without mangling.
> >
> > No, for now, if you want to do this, do it in the serio code only, let's
> > clean up the locking first before we do this in the core.
> >
>
> *confused* This patch is completely independent from any locking issues in
> driver core...
I agree, it's a convient excuse to use to keep any other driver core
changes from happening right now :)
> It is just 2 flags in device and driver structures that are checked in
> device_attach and driver_attach.
But I'm not so sure we want to add this to the driver core yet. We can
discuss this after the locking stuff is finished, ok?
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-17 18:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 22:37 [RFC] [PATCH] driver core: allow userspace to unbind drivers from devices Greg KH
2004-11-09 23:36 ` Dmitry Torokhov
2004-11-10 0:33 ` Greg KH
2004-11-10 3:49 ` Dmitry Torokhov
2004-11-16 5:54 ` Greg KH
2004-11-16 20:43 ` Dmitry Torokhov
2004-11-16 23:08 ` Greg KH
2004-11-17 7:00 ` Dmitry Torokhov
2004-11-17 17:55 ` Greg KH [this message]
2004-11-16 6:13 ` Adam Belay
2004-11-16 6:37 ` Dmitry Torokhov
2004-11-16 7:04 ` Adam Belay
2004-11-16 20:22 ` Greg KH
2004-11-16 21:09 ` Dmitry Torokhov
2004-11-16 20:17 ` Greg KH
2004-11-17 7:07 ` Dmitry Torokhov
2004-11-17 17:53 ` Greg KH
2004-11-17 19:01 ` Dmitry Torokhov
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=20041117175504.GE28285@kroah.com \
--to=greg@kroah.com \
--cc=ambx1@neo.rr.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=tj@home-tj.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