From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [patch 2.6.23-omap] misc musb tweaks
Date: Sun, 14 Oct 2007 18:44:32 -0700 [thread overview]
Message-ID: <200710141844.32657.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0710142127330.32416-100000@netrider.rowland.org>
On Sunday 14 October 2007, Alan Stern wrote:
> On Sun, 14 Oct 2007, David Brownell wrote:
>
> > > What else should we still fix before submitting to linux-usb-devel?
> >
> > I don't see much of a reason why it shouldn't go upstream "now"...
>
> The host part will need a bunch of changes to put it in line with the
> new urb->status stuff. Without that it won't even compile. Not
> difficult to do, just something to keep in the back of your mind...
And that's all in the current kernel.org GIT tree, ISTR ...
- Dave
next parent reply other threads:[~2007-10-15 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0710142127330.32416-100000@netrider.rowland.org>
2007-10-15 1:44 ` David Brownell [this message]
2007-10-15 14:46 ` [patch 2.6.23-omap] misc musb tweaks Tony Lindgren
2007-10-12 21:26 David Brownell
2007-10-14 17:16 ` Tony Lindgren
2007-10-15 1:10 ` 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=200710141844.32657.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.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