From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Krzysztof Kozlowski <krzk@kernel.org>,
corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH docs] docs: maintainer: document expectations of small time maintainers
Date: Tue, 18 Jul 2023 18:02:36 +0200 [thread overview]
Message-ID: <2c4f2031-db2d-92c4-5476-dfd813f93d50@leemhuis.info> (raw)
In-Reply-To: <20230718083753.2d1e003a@kernel.org>
On 18.07.23 17:37, Jakub Kicinski wrote:
> On Sat, 15 Jul 2023 12:31:02 +0200 Linux regression tracking (Thorsten
> Leemhuis) wrote:
>> Maintainers must ensure severe problems in their code reported to them
BTW: I wonder if "reported to them" should be removed. Or maybe it
should be "they become aware of" instead, as they might be reported to
of the the contributors to the subsystem the maintainer handles. Not
sure. Currently I think removing might be better. Judge yourself.
>> are resolved in a timely manner: security vulnerabilities, regressions,
>> compilation errors, data loss, kernel crashes, and bugs of similar scope.
>
> SG, thanks for the suggestion!
+1
> One edit - I'd like to remove "security vulnerabilities" from the list.
> Security implications are an axis on which bug can be evaluated, one of
> many. All kernel bugs have some security implications. Placing them as
> a category like crashes, lockups or compiler errors could deepen the
> confusion.
I don't really care, but that could be avoided with something like
"security vulnerabilities known to be exploitable".
Cioa, Thorsten
next prev parent reply other threads:[~2023-07-18 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 22:34 [PATCH docs] docs: maintainer: document expectations of small time maintainers Jakub Kicinski
2023-07-14 4:36 ` Krzysztof Kozlowski
2023-07-14 5:05 ` Matthew Wilcox
2023-07-14 17:10 ` Jakub Kicinski
2023-07-15 10:31 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-17 7:49 ` Krzysztof Kozlowski
2023-07-17 14:37 ` Greg KH
2023-07-18 15:37 ` Jakub Kicinski
2023-07-18 16:02 ` Thorsten Leemhuis [this message]
2023-07-17 7:44 ` Krzysztof Kozlowski
2023-07-14 6:24 ` Thorsten Leemhuis
2023-07-14 17:22 ` Jakub Kicinski
2023-07-14 17:59 ` Mark Brown
2023-07-14 18:34 ` Jakub Kicinski
2023-07-14 20:02 ` Mark Brown
2023-07-15 6:38 ` Greg KH
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=2c4f2031-db2d-92c4-5476-dfd813f93d50@leemhuis.info \
--to=linux@leemhuis.info \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=workflows@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).