From: Mark Brown <broonie@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH docs] docs: maintainer: document expectations of small time maintainers
Date: Fri, 14 Jul 2023 18:59:08 +0100 [thread overview]
Message-ID: <a7d0381c-c99e-4dba-9156-cc07a86bdc39@sirena.org.uk> (raw)
In-Reply-To: <20230714102218.687ee2ea@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Fri, Jul 14, 2023 at 10:22:18AM -0700, Jakub Kicinski wrote:
> On Fri, 14 Jul 2023 08:24:38 +0200 Thorsten Leemhuis wrote:
> > Also: It's totally normal that commercial vendor contribute basic
> > drivers with known problems and missing features (some of which will
> > never be implemented). The latter will be considered a "bug" for quite a
> > few users that read this. Those suddenly thus might becomes something
> > they now "must" fix, which leads to questions: how fast? just in
> > mainline, or in stable, too?
> If we try to fend off anyone who doesn't understand common meaning
> of words the document will be very long and painful to read.
That's true, but "bug" is one of those things where there is a frequent
disconnect on definitions, and when coupled with the must respond bit I
can see things going wrong.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-14 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 22:34 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
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 [this message]
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=a7d0381c-c99e-4dba-9156-cc07a86bdc39@sirena.org.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--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