From: Jakub Kicinski <kuba@kernel.org>
To: Edward Cree <ecree.xilinx@gmail.com>
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:42:46 -0700 [thread overview]
Message-ID: <20230720144246.7e3507d1@kernel.org> (raw)
In-Reply-To: <50164116-9d12-698d-f552-96b52c718749@gmail.com>
On Thu, 20 Jul 2023 19:23:56 +0100 Edward Cree wrote:
> Does this apply even to "checkpatch cleanup patch spam", where other patches
> sprayed from the same source (perhaps against other drivers) have already
> been nacked as worthless churn?
For networking you can check patchwork, if it's already marked
as rejected or such - there's no need to respond.
> I've generally been assuming I can ignore those, do I need to make
> sure to explicitly respond with typically a repeat of what's already
> been said elsewhere?
Repeating the same thing over and over is sadly a part of being
a maintainer, tho.
next prev parent reply other threads:[~2023-07-20 21:42 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
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 [this message]
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=20230720144246.7e3507d1@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=benjamin.poirier@gmail.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ecree.xilinx@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.