From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linux-USB <linux-usb-devel@lists.sourceforge.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH] USB fixes for 2.6.10-rc3
Date: Fri, 10 Dec 2004 15:48:43 +1100 [thread overview]
Message-ID: <1102654123.22745.23.camel@gaston> (raw)
In-Reply-To: <20041210001932.GA10889@kroah.com>
> Hm, I'll look into doing that after 2.6.10, as it does make more sense
> in the long run.
I agree. I remember playing with a USB driver in linux a while ago and
spending some time trying to figure out what was going on with byte
order :) I'd rather keep the raw HW (that is: well defined) byte order
in those fields, and let sparse catch drivers who don't properly convert
before use.
Ben.
next prev parent reply other threads:[~2004-12-10 4:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 23:09 [BK PATCH] USB fixes for 2.6.10-rc3 Greg KH
2004-12-09 23:41 ` Linus Torvalds
2004-12-09 23:57 ` Greg KH
2004-12-10 0:08 ` Linus Torvalds
2004-12-10 0:19 ` Greg KH
2004-12-10 4:48 ` Benjamin Herrenschmidt [this message]
2004-12-11 15:21 ` linjia02
2004-12-10 0:12 ` [linux-usb-devel] " David Brownell
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=1102654123.22745.23.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=torvalds@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