From: Greg KH <greg@kroah.com>
To: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] convert struct usb_device_descriptor to native endian
Date: Mon, 20 Dec 2004 15:40:13 -0800 [thread overview]
Message-ID: <20041220234013.GB21870@kroah.com> (raw)
In-Reply-To: <20041220233904.GA21870@kroah.com>
On Mon, Dec 20, 2004 at 03:39:04PM -0800, Greg KH wrote:
> As discussed last week, (see
> http://article.gmane.org/gmane.linux.kernel/262089 for the thread) I've
> committed the following patch to the USB bk trees.
>
> Consider this a "heads up" for any USB drivers that are outside of the
> main kernel tree (and if there are any, why not submit them for
> inclusion?)
Note, I didn't fix up the usb gadget drivers yet, they still need a bit
more work to be sparse clean. I'll be doing that, and changing the
remaining 16bit USB data fields next, but those changes will not be as
intrusive or as big as this one was.
thanks,
greg k-h
next prev parent reply other threads:[~2004-12-20 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 23:39 [PATCH] convert struct usb_device_descriptor to native endian Greg KH
2004-12-20 23:40 ` Greg KH [this message]
2004-12-21 0:22 ` [PATCH] USB: change wTotalLength field in struct usb_config_descriptor to be __le16 Greg KH
2004-12-21 1:15 ` 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=20041220234013.GB21870@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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