From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-doc@vger.kernel.org, Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH] doc: process: Add "Root-caused-by" and "Suggested-by"
Date: Wed, 21 Feb 2018 18:13:20 -0800 [thread overview]
Message-ID: <1519265600.4326.22.camel@perches.com> (raw)
In-Reply-To: <20180222003749.GA4724@beast>
On Wed, 2018-02-21 at 16:37 -0800, Kees Cook wrote:
> As recently pointed out by Linus, "Root-caused-by" is a good tag to include
> since it can indicate significantly more work than "just" a Reported-by.
> This adds it and "Suggested-by" (which was also missing) to the documented
> list of tags. Additionally updates checkpatch.pl to match the process docs.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -464,9 +464,11 @@ our $logFunctions = qr{(?x:
> our $signature_tags = qr{(?xi:
> Signed-off-by:|
> Acked-by:|
> + Co-Developed-by:|
> Tested-by:|
> Reviewed-by:|
> Reported-by:|
> + Root-caused-by:|
> Suggested-by:|
> To:|
> Cc:
Patch does not match commit description
next prev parent reply other threads:[~2018-02-22 2:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 0:37 [PATCH] doc: process: Add "Root-caused-by" and "Suggested-by" Kees Cook
2018-02-22 2:13 ` Joe Perches [this message]
2018-02-22 2:16 ` Kees Cook
2018-02-22 4:43 ` Randy Dunlap
2018-02-22 6:03 ` Kees Cook
2018-02-22 17:29 ` Randy Dunlap
2018-02-22 17:40 ` Jonathan Corbet
2018-02-22 23:52 ` Joe Perches
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=1519265600.4326.22.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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