From: Jakob Koschel <jkl820.git@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 jc_docs tree
Date: Thu, 19 Jan 2023 22:59:41 +0100 [thread overview]
Message-ID: <3804F4A3-7CD0-4A77-8E4A-07459F9DC64B@gmail.com> (raw)
In-Reply-To: <87ilh26vrd.fsf@meer.lwn.net>
> On 19. Jan 2023, at 22:48, Jonathan Corbet <corbet@lwn.net> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>
>> Hi all,
>>
>> Commit
>>
>> 6b25b190a9a3 ("docs/scripts/gdb: add necessary make scripts_gdb step")
>>
>> is missing a Signed-off-by from its author.
>
> Sigh...my tooling is supposed to catch that... Patch dropped; Jakob,
> would you like to send me a properly signed-off version?
whops, it was the first time using b4 submit and I can see Sined-off-by in the email
(https://lore.kernel.org/linux-kernel/20230112-documentation-gdb-v1-1-09ab556e9124@gmail.com/)
was it perhaps put in the wrong place?
I'll be taking a look!
>
> Thanks,
>
> jon
next prev parent reply other threads:[~2023-01-19 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 21:34 linux-next: Signed-off-by missing for commit in the jc_docs tree Stephen Rothwell
2023-01-19 21:48 ` Jonathan Corbet
2023-01-19 21:59 ` Jakob Koschel [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 6:11 Stephen Rothwell
2020-10-21 21:55 Stephen Rothwell
2020-10-21 22:19 ` Jonathan Corbet
2020-10-22 6:55 ` Zheng, Fam
2020-08-24 23:13 Stephen Rothwell
2020-08-24 23:18 ` Jonathan Corbet
2020-05-25 22:01 Stephen Rothwell
2020-05-26 14:44 ` Jonathan Corbet
2020-06-05 20:28 ` Alexander A. Klimov
2020-06-05 20:34 ` Jonathan Corbet
2019-06-26 22:01 Stephen Rothwell
2019-06-26 22:09 ` Jonathan Corbet
2018-05-10 21:40 Stephen Rothwell
2018-05-10 21:44 ` Jonathan Corbet
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=3804F4A3-7CD0-4A77-8E4A-07459F9DC64B@gmail.com \
--to=jkl820.git@gmail.com \
--cc=corbet@lwn.net \
--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;
as well as URLs for NNTP newsgroup(s).