From: Dan Carpenter <dan.carpenter@oracle.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Florian Eckert <fe@dev.tdt.de>
Subject: Re: [PATCH v1 1/1] docs: process: submitting-patches: Clarify the Reported-by usage
Date: Thu, 3 Mar 2022 12:45:09 +0300 [thread overview]
Message-ID: <20220303094509.GA9912@kili> (raw)
In-Reply-To: <20220127155334.47154-1-andriy.shevchenko@linux.intel.com>
On Thu, Jan 27, 2022 at 05:53:34PM +0200, 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>
> ---
I've always lobbied for a Fixes-from for bug fixes that get folded into
the original patch but I also kind of agree with Dan Williams that
Reported-by tags are fine for new code.
https://lore.kernel.org/all/CAPcyv4gbgDMGBQ3t4q1EckELbMG5JXi10YuzLsMjFns67od=sw@mail.gmail.com/
Everyone can figure it out from the context that kbuild bot didn't
really tell anyone to write a new driver. It's just the reported-by
count that's used to justify funding a team of devs.
regards,
dan carpenter
prev parent reply other threads:[~2022-03-03 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 15:53 [PATCH v1 1/1] docs: process: submitting-patches: Clarify the Reported-by usage Andy Shevchenko
2022-01-27 16:08 ` Jonathan Corbet
2022-01-27 16:28 ` Andy Shevchenko
2022-01-28 9:31 ` Alexander Dahl
2022-01-28 13:44 ` Matthew Wilcox
2022-01-31 15:18 ` Johan Hovold
2022-01-31 15:34 ` Andy Shevchenko
2022-01-31 16:47 ` Johan Hovold
2022-01-31 18:16 ` Andy Shevchenko
2022-02-01 8:51 ` Johan Hovold
2022-03-03 9:54 ` Dan Carpenter
2022-03-03 13:27 ` Johan Hovold
2022-03-03 13:51 ` Dan Carpenter
2022-03-03 9:45 ` Dan Carpenter [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=20220303094509.GA9912@kili \
--to=dan.carpenter@oracle.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=fe@dev.tdt.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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