From: Roger Quadros <rogerq@kernel.org>
To: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the usb tree
Date: Tue, 30 May 2023 10:29:49 +0300 [thread overview]
Message-ID: <e4f29418-6612-cbe6-10be-7fb3b078caac@kernel.org> (raw)
In-Reply-To: <2023053050-patrol-item-1844@gregkh>
On 30/05/2023 10:27, Greg KH wrote:
> On Tue, May 30, 2023 at 08:16:11AM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Commit
>>
>> b4a4be847184 ("USB: fix up merge of 6.4-rc4 into usb-next")
>>
>> is missing a Signed-off-by from its author.
>
> Known issue, it was part of a thread as to how to fix up the merge and I
> wanted to give the original author credit for it.
>
Thanks Greg & Stephen.
I have no issues with the patch.
--
cheers,
-roger
prev parent reply other threads:[~2023-05-30 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 22:16 linux-next: Signed-off-by missing for commit in the usb tree Stephen Rothwell
2023-05-30 7:27 ` Greg KH
2023-05-30 7:29 ` Roger Quadros [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=e4f29418-6612-cbe6-10be-7fb3b078caac@kernel.org \
--to=rogerq@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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