From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Florian Eckert <fe@dev.tdt.de>
Subject: Re: [PATCH v2 1/1] docs: process: submitting-patches: Clarify the Reported-by usage
Date: Thu, 27 Jan 2022 11:54:33 -0700 [thread overview]
Message-ID: <87h79pqaae.fsf@meer.lwn.net> (raw)
In-Reply-To: <1e2e99f6-e9bf-7d93-9629-3d70275c77f4@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> On 1/27/22 08:32, Andy Shevchenko wrote:
>> It's unclear from "Submitting Patches" documentation that Reported-by
>> is not supposed to be used against new features. (It's more clear
>> in the section 5.4 "Patch formatting and changelogs" of the "A guide
>> to the Kernel Development Process", where it suggests that change
>> should fix something existing in the kernel. Clarify the Reported-by
>> usage in the "Submitting Patches".
>>
>> Reported-by: Florian Eckert <fe@dev.tdt.de>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>> v2: rephrased as suggested by Jonathan
>> Documentation/process/submitting-patches.rst | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
>> index 31ea120ce531..fb496b2ebfd3 100644
>> --- a/Documentation/process/submitting-patches.rst
>> +++ b/Documentation/process/submitting-patches.rst
>> @@ -495,7 +495,8 @@ Using Reported-by:, Tested-by:, Reviewed-by:, Suggested-by: and Fixes:
>> The Reported-by tag gives credit to people who find bugs and report them and it
>> hopefully inspires them to help us again in the future. Please note that if
>> the bug was reported in private, then ask for permission first before using the
>> -Reported-by tag.
>> +Reported-by tag. The tag is intended for bugs; please do not use it to credit
>> +feature requests.
>>
>
> LGTM.
> Although it could refer to Suggested-by. :)
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
Applied, thanks.
jon
prev parent reply other threads:[~2022-01-27 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 16:32 [PATCH v2 1/1] docs: process: submitting-patches: Clarify the Reported-by usage Andy Shevchenko
2022-01-27 17:21 ` Randy Dunlap
2022-01-27 17:54 ` Andy Shevchenko
2022-01-27 18:54 ` Jonathan Corbet [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=87h79pqaae.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fe@dev.tdt.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.