From: "Zheng, Fam" <famzheng@amazon.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"corbet@lwn.net" <corbet@lwn.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the jc_docs tree
Date: Thu, 22 Oct 2020 06:55:44 +0000 [thread overview]
Message-ID: <4b2a547e58b700455f6732f13cac32cb74568e96.camel@amazon.com> (raw)
In-Reply-To: <20201021161944.14fb7d9f@lwn.net>
On Wed, 2020-10-21 at 16:19 -0600, Jonathan Corbet wrote:
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you can confirm the sender
> and know the content is safe.
>
>
>
> On Thu, 22 Oct 2020 08:55:42 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Commit
> >
> > 9467739c239d ("docs: Add two missing entries in vm sysctl index")
> >
> > is missing a Signed-off-by from its author.
>
> Argh, I should have caught that. I'd blame wildfires, but that would
> be
> lame.
>
> Offending commit removed; Fam, can you send a properly signed-off
> replacement? Meanwhile I'm going to go look at my tooling so this
> doesn't
> happen again...
My bad, I'll fix my setup.
V2 sent.
Fam
>
> Thanks for the heads-up,
>
> jon
next prev parent reply other threads:[~2020-10-22 6:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 21:55 linux-next: Signed-off-by missing for commit in the jc_docs tree Stephen Rothwell
2020-10-21 22:19 ` Jonathan Corbet
2020-10-22 6:55 ` Zheng, Fam [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 6:11 Stephen Rothwell
2023-01-19 21:34 Stephen Rothwell
2023-01-19 21:48 ` Jonathan Corbet
2023-01-19 21:59 ` Jakob Koschel
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=4b2a547e58b700455f6732f13cac32cb74568e96.camel@amazon.com \
--to=famzheng@amazon.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).