From: Jakub Kicinski <kuba@kernel.org>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [ANN] pylint and shellcheck
Date: Fri, 6 Jun 2025 06:33:27 -0700 [thread overview]
Message-ID: <20250606063327.186ee244@kernel.org> (raw)
In-Reply-To: <m2tt4tt3wv.fsf@gmail.com>
On Fri, 06 Jun 2025 14:06:56 +0100 Donald Hunter wrote:
> I could have patches ready for the merge window opening. What's best, a
> patch per type of error, or some other split?
Maybe, say, patch per error type for those that have > 2 hits,
and for the less common ones.. improvise? :)
prev parent reply other threads:[~2025-06-06 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 19:06 [ANN] pylint and shellcheck Jakub Kicinski
2025-06-04 7:27 ` Simon Horman
2025-06-04 13:36 ` Przemek Kitszel
2025-06-04 9:41 ` Donald Hunter
2025-06-04 23:43 ` Jakub Kicinski
2025-06-05 9:02 ` Donald Hunter
2025-06-05 14:26 ` Jakub Kicinski
2025-06-06 13:06 ` Donald Hunter
2025-06-06 13:33 ` Jakub Kicinski [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=20250606063327.186ee244@kernel.org \
--to=kuba@kernel.org \
--cc=donald.hunter@gmail.com \
--cc=netdev@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).