From: Jakub Kicinski <kuba@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: corbet@lwn.net, Andrew Lunn <andrew@lunn.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Mark Brown <broonie@kernel.org>,
Leon Romanovsky <leonro@nvidia.com>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux@leemhuis.info, kvalo@kernel.org,
benjamin.poirier@gmail.com
Subject: Re: [PATCH docs v3] docs: maintainer: document expectations of small time maintainers
Date: Thu, 20 Jul 2023 14:37:46 -0700 [thread overview]
Message-ID: <20230720143746.1adb159a@kernel.org> (raw)
In-Reply-To: <20230720-proxy-smile-f1b882906ded@spud>
On Thu, 20 Jul 2023 16:15:26 +0100 Conor Dooley wrote:
> ..I noticed that none of these sections address actually testing the
> code they're responsible for on a (semi-)regular basis. Sure, that comes
> as part of reviewing the patches for their code, but changes to other
> subsystems that a driver/feature maintainer probably would not have been
> CCed on may cause problems for the code they maintain.
> If we are adding a doc about best-practice for maintainers, I think we
> should be encouraging people to test regularly.
I think our testing story is too shaky to make that a requirement.
Differently put - I was never able to get good upstream testing running
when I worked for a vendor myself so I wouldn't know how to draw
the lines.
next prev parent reply other threads:[~2023-07-20 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 18:32 [PATCH docs v3] docs: maintainer: document expectations of small time maintainers Jakub Kicinski
2023-07-20 15:15 ` Conor Dooley
2023-07-20 21:37 ` Jakub Kicinski [this message]
2023-07-20 22:23 ` Conor Dooley
2023-07-20 18:23 ` Edward Cree
2023-07-20 18:26 ` Greg Kroah-Hartman
2023-07-20 18:31 ` Mark Brown
2023-07-20 21:42 ` Jakub Kicinski
2023-07-21 7:46 ` Martin Habets
2023-07-21 8:38 ` Simon Horman
2023-07-21 19:53 ` Jonathan Corbet
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=20230720143746.1adb159a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=benjamin.poirier@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=kvalo@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=netdev@vger.kernel.org \
--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 NNTP newsgroup(s).