From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [GIT PULL] usb: chipidea: changes for v5.3-rc1
Date: Fri, 5 Jul 2019 07:20:35 +0200 [thread overview]
Message-ID: <20190705052035.GC15821@kroah.com> (raw)
In-Reply-To: <AM0PR04MB5314EF9667220C996B5860378BF50@AM0PR04MB5314.eurprd04.prod.outlook.com>
On Fri, Jul 05, 2019 at 03:32:40AM +0000, Peter Chen wrote:
> The following changes since commit 8ea5b2abd07e2280a332bd9c1a7f4dd15b9b6c13:
>
> Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2019-05-09 19:35:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git/ tags/usb-ci-v5.3-rc1
Pulled and pushed out, thanks.
greg k-h
prev parent reply other threads:[~2019-07-05 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 3:32 [GIT PULL] usb: chipidea: changes for v5.3-rc1 Peter Chen
2019-07-05 5:20 ` gregkh [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=20190705052035.GC15821@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.com \
/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).