From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] musb: Export musb_root_disconnect for use in modules
Date: Thu, 22 Sep 2016 19:28:42 +0200 [thread overview]
Message-ID: <20160922172842.GA23726@kroah.com> (raw)
In-Reply-To: <20160922171526.GR7994@sirena.org.uk>
On Thu, Sep 22, 2016 at 06:15:26PM +0100, Mark Brown wrote:
> On Thu, Sep 22, 2016 at 08:30:16AM -0500, Bin Liu wrote:
> > On Wed, Sep 21, 2016 at 03:51:33PM -0500, Bin Liu wrote:
>
> > > Applied. Thanks.
>
> > Removed it from my tree, since Greg already picked it.
>
> It's not showing in today's -next...
It probably missed the cut-off, should be there tomorrow.
next prev parent reply other threads:[~2016-09-22 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 10:08 [PATCH v2] musb: Export musb_root_disconnect for use in modules Hans de Goede
2016-09-21 20:51 ` Bin Liu
2016-09-22 13:30 ` Bin Liu
2016-09-22 17:15 ` Mark Brown
2016-09-22 17:28 ` Greg Kroah-Hartman [this message]
2016-09-22 17:40 ` Mark Brown
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=20160922172842.GA23726@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).