From: Greg KH <greg@kroah.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-usb@vger.kernel.org, Felipe Balbi <felipe.balbi@nokia.com>,
Cliff Cai <cliff.cai@analog.com>, Ian Jeffray <ian@jeffray.co.uk>,
linux-kernel@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
stable-review@kernel.org, stable@kernel.org
Subject: Re: [stable] [PATCH] USB: musb: fix Blackfin building after power updates
Date: Mon, 24 May 2010 11:50:00 -0700 [thread overview]
Message-ID: <20100524185000.GB8627@kroah.com> (raw)
In-Reply-To: <1274582948-11499-1-git-send-email-vapier@gentoo.org>
On Sat, May 22, 2010 at 10:49:08PM -0400, Mike Frysinger wrote:
> From: Ian Jeffray <ian@jeffray.co.uk>
>
> The new MUSB power code needs musb_read_txhubport() to return a value (so
> stub it as 0 like the other Blackfin hub funcs). It also needs new helper
> functions for saving/restoring context, so change the apparently unused
> musb_platform_{suspend,resume} to musb_platform_{save,restore}_context in
> the Blackfin code.
>
> Signed-off-by: Ian Jeffray <ian@jeffray.co.uk>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> Note: this is for 2.6.34.x and 2.6.35
> Note: i believe this is what we want, but Cliff is free to correct me ;)
>
> drivers/usb/musb/blackfin.c | 12 ++++++++++++
> drivers/usb/musb/musb_regs.h | 3 ++-
Note, I'm refusing to take any musb patch unless it comes from Felipe
due to the constant bickering from a number of the musb developers,
which is starting to really annoy me and contemplate warming up my kill
file...
So please work with him to get this agreed apon and have him forward it
to me when ready, that's the only way I'm going to accept it.
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-24 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 2:49 [PATCH] USB: musb: fix Blackfin building after power updates Mike Frysinger
2010-05-23 8:42 ` Sergei Shtylyov
2010-05-23 8:49 ` Mike Frysinger
2010-05-24 18:50 ` Greg KH [this message]
2010-05-24 18:52 ` [Uclinux-dist-devel] [stable] " 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=20100524185000.GB8627@kroah.com \
--to=greg@kroah.com \
--cc=cliff.cai@analog.com \
--cc=felipe.balbi@nokia.com \
--cc=ian@jeffray.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.