From: David Brownell <david-b@pacbell.net>
To: Greg KH <gregkh@suse.de>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
khilman@deeprootsystems.com
Subject: Re: [GIT PATCH] USB patches for 2.6-git
Date: Wed, 7 Jan 2009 14:48:06 -0800 [thread overview]
Message-ID: <200901071448.06565.david-b@pacbell.net> (raw)
In-Reply-To: <20090107212801.GA21012@suse.de>
On Wednesday 07 January 2009, Greg KH wrote:
> > I am dissatisfied how MUSB patches have been handled in general -- this
> > is not the first breakage, and the valid patches have been lost, so DaVinci
> > MUSB code keeps being broken since early 2.6.27-rc's (!) up to this time...
>
> I agree, there's a big disconnect somewhere, I'm sorry about that. I
> now see David's request to change this patch in my archives :(
There's also that OTG patch to merge ...
After I see this in mainline, I'll send any build fixes needed.
If musb-on-DaVinci can't make 2.6.27, it should be able to finally
make it in 2.6.29 ... :(
What would really suck is if the OMAP3 support manages to work
in mainline but DaVinci is still broken. At the time the driver
was submitted (for 2.6.27), DaVinci was the only platform to
have a set of "everything works" patches submitted ...
- Dave
next prev parent reply other threads:[~2009-01-07 22:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 19:24 [GIT PATCH] USB patches for 2.6-git Greg KH
2009-01-07 20:23 ` Sergei Shtylyov
2009-01-07 21:28 ` Greg KH
2009-01-07 21:42 ` Sergei Shtylyov
2009-01-07 21:54 ` Andrew Morton
2009-01-07 22:48 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-17 21:05 Greg KH
2009-02-27 22:45 Greg KH
2009-02-09 19:31 Greg KH
2009-01-27 23:49 Greg KH
2009-01-27 23:56 ` Greg KH
2008-12-17 19:27 Greg KH
2008-11-13 23:02 Greg KH
2008-11-14 4:06 ` Gupta, Ajay Kumar
2008-11-14 19:15 ` Greg KH
2008-11-14 19:40 ` Sergei Shtylyov
2008-11-14 19:59 ` Greg KH
2008-11-14 20:10 ` Sergei Shtylyov
2008-11-14 20:55 ` Greg KH
2008-11-14 21:02 ` Sergei Shtylyov
2008-11-14 21:07 ` Greg KH
2008-10-29 22:38 Greg KH
2008-10-17 22:00 Greg KH
2008-10-17 22:47 ` Linus Torvalds
2008-10-17 23:00 ` Greg KH
2008-10-17 23:09 ` Greg KH
[not found] ` <gdfauh$hsp$1@ger.gmane.org>
2008-10-19 17:29 ` Greg KH
2008-10-19 19:37 ` Dmitry
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=200901071448.06565.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
--cc=torvalds@linux-foundation.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