From: Felipe Balbi <balbi@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [GIT PULL] USB: changes for v5.6 merge window
Date: Wed, 15 Jan 2020 12:33:41 +0200 [thread overview]
Message-ID: <8736ch6mbe.fsf@kernel.org> (raw)
In-Reply-To: <20200115093746.GA3177342@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi,
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Wed, Jan 15, 2020 at 10:28:13AM +0100, Greg Kroah-Hartman wrote:
>> 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?
>>
>
> I did a pull, and get this problem when checking the patches:
>
> Commit: 6a6ae4e8e926 ("usb: gadget: f_ncm: Use atomic_t to track in-flight request")
> Fixes tag: Fixes: 40d133d7f5426 ("usb: gadget: f_ncm: convert to new function interface
> Has these problem(s):
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
Oh, I missed those.
> I'll go fix it up, but that will break your tree if you try to merge as
Thanks for fixing. I'll reset my tree to yours.
> I will have to rebase :(
no worries.
Out of curiosity, what are you using to flag those? Is checkpatch doing
that now?
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-01-15 10:32 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
2020-01-15 9:37 ` Greg Kroah-Hartman
2020-01-15 10:33 ` Felipe Balbi [this message]
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=8736ch6mbe.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.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).