From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Felipe Balbi <balbi@kernel.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [GIT PULL] USB: changes for v5.6 merge window
Date: Wed, 15 Jan 2020 10:28:13 +0100 [thread overview]
Message-ID: <20200115092813.GA3153837@kroah.com> (raw)
In-Reply-To: <878sm96pzf.fsf@kernel.org>
On Wed, Jan 15, 2020 at 11:14:28AM +0200, Felipe Balbi wrote:
>
> Hi Greg,
>
> here's my pull request for v5.6 merge window. If you want anything to be
> changed, let me know.
Did you send this twice? Any difference?
next prev parent reply other threads:[~2020-01-15 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 9:14 [GIT PULL] USB: changes for v5.6 merge window Felipe Balbi
2020-01-15 9:28 ` Greg Kroah-Hartman [this message]
2020-01-15 9:37 ` Greg Kroah-Hartman
2020-01-15 10:33 ` Felipe Balbi
2020-01-15 12:03 ` Greg Kroah-Hartman
2020-01-15 12:06 ` Felipe Balbi
2020-01-15 12:11 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 9:13 Felipe Balbi
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=20200115092813.GA3153837@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@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;
as well as URLs for NNTP newsgroup(s).