From: Greg KH <gregkh@linuxfoundation.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>
Subject: Re: [GIT PULL] USB patches
Date: Thu, 20 Feb 2014 15:27:01 -0800 [thread overview]
Message-ID: <20140220232701.GA8561@kroah.com> (raw)
In-Reply-To: <1392910010-25612-1-git-send-email-balbi@ti.com>
On Thu, Feb 20, 2014 at 09:26:50AM -0600, Felipe Balbi wrote:
> Hi Greg,
>
> Here's a pull request for final round of fixes. All patches have
> been soaking for a long time in linux-usb, passed my 300 randconfig
> builds and work on real HW (where applicable).
>
> This pull request is based off of greg/usb-linus in order for me
> to avoid merging patches you had already merged during my time
> off.
>
> Please consider merging this tag on your greg/usb-linus.
Pulled and pushed out, thanks.
greg k-h
next prev parent reply other threads:[~2014-02-20 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 15:26 [GIT PULL] USB patches Felipe Balbi
2014-02-20 23:27 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-23 16:53 Felipe Balbi
2014-12-24 0:06 ` Greg KH
2015-01-14 17:48 Felipe Balbi
2015-01-15 0:28 ` Greg KH
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=20140220232701.GA8561@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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