linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2 1/1] docs: process: submitting-patches: Clarify the Reported-by usage
@ 2022-01-27 16:32 Andy Shevchenko
  2022-01-27 17:21 ` Randy Dunlap
  0 siblings, 1 reply; 4+ messages in thread
From: Andy Shevchenko @ 2022-01-27 16:32 UTC (permalink / raw)
  To: Jonathan Corbet, linux-doc, linux-kernel; +Cc: Andy Shevchenko, Florian Eckert

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.
 
 A Tested-by: tag indicates that the patch has been successfully tested (in
 some environment) by the person named.  This tag informs maintainers that
-- 
2.34.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH v2 1/1] docs: process: submitting-patches: Clarify the Reported-by usage
  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
  0 siblings, 2 replies; 4+ messages in thread
From: Randy Dunlap @ 2022-01-27 17:21 UTC (permalink / raw)
  To: Andy Shevchenko, Jonathan Corbet, linux-doc, linux-kernel; +Cc: Florian Eckert



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>

thanks.

>  A Tested-by: tag indicates that the patch has been successfully tested (in
>  some environment) by the person named.  This tag informs maintainers that

-- 
~Randy

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v2 1/1] docs: process: submitting-patches: Clarify the Reported-by usage
  2022-01-27 17:21 ` Randy Dunlap
@ 2022-01-27 17:54   ` Andy Shevchenko
  2022-01-27 18:54   ` Jonathan Corbet
  1 sibling, 0 replies; 4+ messages in thread
From: Andy Shevchenko @ 2022-01-27 17:54 UTC (permalink / raw)
  To: Randy Dunlap; +Cc: Jonathan Corbet, linux-doc, linux-kernel, Florian Eckert

On Thu, Jan 27, 2022 at 09:21:21AM -0800, Randy Dunlap wrote:
> On 1/27/22 08:32, Andy Shevchenko wrote:

...

> > -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.  :)

The main issue here is that automated CIs may suggest people to include the tag.
And people (especially who are new in the community) tend to obey without a
doubt.

> Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks!

-- 
With Best Regards,
Andy Shevchenko



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v2 1/1] docs: process: submitting-patches: Clarify the Reported-by usage
  2022-01-27 17:21 ` Randy Dunlap
  2022-01-27 17:54   ` Andy Shevchenko
@ 2022-01-27 18:54   ` Jonathan Corbet
  1 sibling, 0 replies; 4+ messages in thread
From: Jonathan Corbet @ 2022-01-27 18:54 UTC (permalink / raw)
  To: Randy Dunlap, Andy Shevchenko, linux-doc, linux-kernel; +Cc: Florian Eckert

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-01-27 18:54 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).