From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
david-b@pacbell.net, khilman@deeprootsystems.com
Subject: Re: [GIT PATCH] USB patches for 2.6-git
Date: Wed, 07 Jan 2009 23:23:08 +0300 [thread overview]
Message-ID: <49650F2C.9030809@ru.mvista.com> (raw)
In-Reply-To: <20090107192438.GA18146@kroah.com>
Hello.
Greg KH wrote:
> Here is the set of USB patches for the 2.6.29-rc1 merge.
>
> They also include the wimax patches, because of a dependancy on a change
> in the USB core to support one of the wimax drivers. The wimax patch
> set has been acked by the network maintainers already, and they agreed
> that it should go through the USB tree to you.
>
> Other than wimax, the patchset includes:
> - some new USB drivers (gadget, host, and serial)
> - USB OTG (on-the-go) device support
> - lots of device id updates
> - renaming in the i2c drivers to move into the proper location
> in the usb tree
> - usb-storage quirk handling cleaned up and reworked
> - sped up the option wireless usb driver speed.
> - removal of info() and warn() usb macros now that the non-usb portions of the kernel have removed their usage of them.
> - lots of minor tweaks and reworks.
>
> Please pull from:
> master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/
>
> All of these patches have been in the -next and -mm releases for a while.
>
> The full patches will be sent to the linux-usb mailing list, if anyone
> wants to see them.
>
> thanks,
>
> greg k-h
>
[...]
> Kevin Hilman (1):
> USB: musb: build fixes for DaVinci
>
NAK this patch. I and David Brownell have asked Greg to pull this
totally broken patch (broken while in MUSB tree, the original patch was
sane) from his tree and all to no avail...
The patch doesn't fix anything and only adds more breakage as it
duplicates musb_platform_set_mode().
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...
WBR, Sergei
next prev parent reply other threads:[~2009-01-07 20:23 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 [this message]
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
-- 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=49650F2C.9030809@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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