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 fixes for v3.13-rc4
Date: Mon, 9 Dec 2013 13:14:06 -0800 [thread overview]
Message-ID: <20131209211406.GA14439@kroah.com> (raw)
In-Reply-To: <1386617210-29054-1-git-send-email-balbi@ti.com>
On Mon, Dec 09, 2013 at 01:26:50PM -0600, Felipe Balbi wrote:
> Hi Greg,
>
> Here's another set of really obvious fixes for this rc cycle. All patches have
> been pending for a while.
>
> Please consider merging on top of your usb-linus branch.
>
> cheers
>
> The following changes since commit 2cf93bea3d7b2dbf1e0ebfa9d381aad1b637e2aa:
>
> usb: gadget: f_mass_storage: call try_to_freeze only when its safe (2013-11-25 11:34:09 -0600)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git tags/fixes-for-v3.13-rc4
Pulled and pushed out now, thanks.
greg k-h
prev parent reply other threads:[~2013-12-09 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 19:26 [GIT PULL] USB fixes for v3.13-rc4 Felipe Balbi
2013-12-09 21:14 ` 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=20131209211406.GA14439@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