From: Greg KH <gregkh@suse.de>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [GIT PATCH] USB fixes for 2.6.31-rc2
Date: Fri, 17 Apr 2009 14:41:10 -0700 [thread overview]
Message-ID: <20090417214110.GA29546@suse.de> (raw)
In-Reply-To: <a4423d670904171412y323c38ech819652633e8674c5@mail.gmail.com>
On Sat, Apr 18, 2009 at 01:12:45AM +0400, Alexander Beregalov wrote:
> Hi Greg
> This patch should be here as well
> http://marc.info/?l=linux-next&m=123996717119063&w=2
> it fixes a build problem introduced by "USB: musb: fix possible panic
> while resuming"
You sent that patch to me earlier today. I need David to ack it, and
for it to live in linux-next a bit before being able to send it to
Linus.
thanks,
greg k-h
prev parent reply other threads:[~2009-04-17 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 19:01 [GIT PATCH] USB fixes for 2.6.31-rc2 Greg KH
2009-04-17 21:12 ` Alexander Beregalov
2009-04-17 21:41 ` Greg KH [this message]
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=20090417214110.GA29546@suse.de \
--to=gregkh@suse.de \
--cc=a.beregalov@gmail.com \
--cc=akpm@linux-foundation.org \
--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