From: Matthew Wilcox <willy@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
Sarah Sharp <sarah.a.sharp@linux.intel.com>
Subject: Re: [PATCH] UAS driver
Date: Tue, 28 Sep 2010 02:45:49 -0400 [thread overview]
Message-ID: <20100928064549.GD3799@linux.intel.com> (raw)
In-Reply-To: <20100928055649.GB8922@kroah.com>
On Mon, Sep 27, 2010 at 10:56:49PM -0700, Greg KH wrote:
> On Tue, Sep 28, 2010 at 01:07:34AM -0400, Matthew Wilcox wrote:
> > +static struct usb_device_id uas_usb_ids[] = {
> > + { USB_INTERFACE_INFO(8, 6, 0x50) },
> > + { USB_INTERFACE_INFO(8, 6, 0x62) },
> > + { USB_INTERFACE_INFO(8, 6, 0xaa) }, /* A prototype */
> > + { }
>
> Don't we have the proper #defines in the usb/ch9.h file that you can use
> here? If not, please add them so that we don't have "magic" numbers.
We've got
#define USB_CLASS_MASS_STORAGE 8
in usb/ch9.h, which I can use.
The other numbers are in include/linux/usb_usual.h, which is actually a pain
to include (I haven't figured out everything I need to do to include it).
What I'd like to do is pull the subclasses and protocols out into a new
include file, include/linux/usb/storage.h to match audio.h. Would you be
likely to accept such a patch?
I don't intend to add 0xaa to a header file ... I see its inclusion in
this driver as a temporary thing, and I'd rather remove support for it
than add it to a header.
next prev parent reply other threads:[~2010-09-28 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 5:07 [PATCH] UAS driver Matthew Wilcox
2010-09-28 5:55 ` Greg KH
[not found] ` <20100928050733.GB3799-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2010-09-28 5:56 ` Greg KH
2010-09-28 6:45 ` Matthew Wilcox [this message]
[not found] ` <20100928064549.GD3799-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2010-09-28 7:06 ` Greg KH
[not found] ` <20100928070613.GA11056-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2010-09-28 7:17 ` Matthew Wilcox
2010-09-28 7:25 ` Greg KH
2010-09-28 7:43 ` 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=20100928064549.GD3799@linux.intel.com \
--to=willy@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.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