From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: Bryan Wu <cooloney@kernel.org>, Felipe Balbi <me@felipebalbi.com>,
linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] MUSB: 2 patches to fix some bug found on Blackfin
Date: Wed, 21 May 2008 10:14:44 -0700 [thread overview]
Message-ID: <200805211014.45170.david-b@pacbell.net> (raw)
In-Reply-To: <20080521155003.GZ23002@atomide.com>
On Wednesday 21 May 2008, Tony Lindgren wrote:
>
> > Great, after I enable the DMA mode 1 on Blackfin and cleanup the code,
> > I will send
> > out the code before you sent them to upstream
>
> Maybe we should get the musb code to USB tree before that? It's been out
> of the scope for linux-omap tree for quite a while now.
I'm all for getting the musb_hdrc driver into the 2.6.27 queue...
I presume there are still some infrastructure changes in usbcore
that block that merge? It'd be nice if we could merge musb_hdrc
without those changes (OTG related) and then update that stuff
separately.
- Dave
next prev parent reply other threads:[~2008-05-21 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 11:01 Bryan Wu
2008-05-17 11:01 ` [PATCH 1/2] MUSB: fix bug - since 2.6.24 urb API changed, giveback function return wrong status Bryan Wu
2008-05-17 11:01 ` [PATCH 2/2] MUSB: Real fix bug 4 usb bugs found on Blackfin Bryan Wu
2008-05-19 15:16 ` Gadiyar, Anand
2008-05-19 15:28 ` Mike Frysinger
2008-05-17 14:37 ` [PATCH 0/2] MUSB: 2 patches to fix some bug " David Brownell
2008-05-19 6:39 ` Bryan Wu
2008-05-19 7:49 ` Felipe Balbi
2008-05-19 8:05 ` Bryan Wu
2008-05-21 15:50 ` Tony Lindgren
2008-05-21 17:14 ` David Brownell [this message]
2008-05-21 19:06 ` Felipe Balbi
2008-05-21 20:04 ` David Brownell
2008-05-21 20:10 ` Mike Frysinger
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=200805211014.45170.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®