From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Greg KH <greg@kroah.com>, Linus Torvalds <torvalds@osdl.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [BK PATCH] USB fixes for 2.6.10-rc3
Date: Thu, 9 Dec 2004 16:12:38 -0800 [thread overview]
Message-ID: <200412091612.38820.david-b@pacbell.net> (raw)
In-Reply-To: <20041209235709.GA8147@kroah.com>
On Thursday 09 December 2004 3:57 pm, Greg KH wrote:
>
> Yeah, it's not the cleanest, and yes, it is just shutting the warning
> up, but that's ok in this case. I guess I could look into doing the
> "two different structures" type thing again, if people don't like things
> like this in different places.
Or maybe just cache a pre-swapped value in the wrapper
structure (usb_host_config)? You don't need to create
a third structure ... and it'd be nice to have simple
rule that the raw descriptors are always in wire order.
- Dave
prev parent reply other threads:[~2004-12-10 0:12 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
2004-12-11 15:21 ` linjia02
2004-12-10 0:12 ` David Brownell [this message]
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=200412091612.38820.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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