From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.org>,
USB list <linux-usb@vger.kernel.org>,
Stefan Kopp <stefan_kopp@agilent.com>,
Marcel Janssen <korgull@home.nl>,
Felipe Balbi <me@felipebalbi.com>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB: add USB test and measurement class driver - round 2
Date: Wed, 27 Aug 2008 16:48:49 -0700 [thread overview]
Message-ID: <20080827234849.GD31264@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0808271513270.2138-100000@iolanthe.rowland.org>
On Wed, Aug 27, 2008 at 03:16:18PM -0400, Alan Stern wrote:
> On Wed, 27 Aug 2008, Oliver Neukum wrote:
>
> > Am Mittwoch 27 August 2008 20:58:08 schrieb Alan Stern:
> > > > And this rule depends on sharing the USB major or not. This needs
> > > > a big fat mention in Documentation.
> > >
> > > You mean that the open/disconnect locking rule applies only to drivers
> > > that call usb_register_dev, i.e, drivers using the USB major. Right?
> >
> > Yes. In fact drivers not using the USB major but their own char devices
> > will need such a lock. This is tricky.
>
> IMO all char-device registration/deregistration routines should use a
> similar rwsem. Then device drivers wouldn't need to worry about it.
>
> > > I agree that it deserves to be mentioned in the documentation
> > > somewhere. Where would be a good place? None of the existing files in
> > > Documentation/usb seem appropriate.
> >
> > The USB major merits a file of its own.
>
> I don't feel competent to start writing such a file. Greg, what do you
> think? Maybe all that's needed to get going is to "borrow" some of the
> material in LDD3. :-)
Well, as the USB chapter in LDD3 "borrowed" heavily from the comments in
the usb code itself, that would only be fair :)
That chapter needs to be reworked. The authors and Oreilly and I are
currently talking about how to do this all in a framework that makes
sense (the current one of a book every few years that quickly gets out
of date doesn't make sense.)
thanks,
greg k-h
next prev parent reply other threads:[~2008-08-28 0:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 17:20 [PATCH] USB: add USB test and measurement class driver - round 2 Greg KH
2008-08-27 18:28 ` Alan Stern
2008-08-27 18:36 ` Greg KH
2008-08-27 18:58 ` Alan Stern
2008-08-27 19:05 ` Oliver Neukum
2008-08-27 19:16 ` Alan Stern
2008-08-27 23:48 ` Greg KH [this message]
2008-08-27 23:47 ` Greg KH
2008-08-28 10:10 ` Oliver Neukum
2008-08-28 16:17 ` Greg KH
2008-08-28 21:29 ` Oliver Neukum
2008-08-28 16:58 ` Marcel Janssen
2008-08-28 20:38 ` Greg KH
2008-08-29 6:57 ` stefan_kopp
2008-08-29 7:46 ` Oliver Neukum
2008-08-29 8:14 ` stefan_kopp
2008-08-29 8:34 ` Oliver Neukum
2008-08-29 9:13 ` stefan_kopp
2008-08-29 11:33 ` Oliver Neukum
2008-08-29 14:39 ` Greg KH
2008-08-29 16:41 ` Marcel Janssen
2008-08-29 20:01 ` Greg KH
2008-08-27 18:37 ` Oliver Neukum
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=20080827234849.GD31264@kroah.com \
--to=greg@kroah.com \
--cc=korgull@home.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=oliver@neukum.org \
--cc=stefan_kopp@agilent.com \
--cc=stern@rowland.harvard.edu \
/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