From: Donald Hunter <donald.hunter@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [ANN] pylint and shellcheck
Date: Wed, 04 Jun 2025 10:41:14 +0100 [thread overview]
Message-ID: <m2ldq7vo79.fsf@gmail.com> (raw)
In-Reply-To: <20250603120639.3587f469@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> Hi!
>
> It's merge window time so I have a bit of time to catch up on random
> things. I added shellcheck, yamllint and pylint:
> https://github.com/linux-netdev/nipa/commit/c0fe53ae533d19c19d2e00955403fb57c3679084
> https://github.com/linux-netdev/nipa/commit/255ee0295a096ee7096bebd9d640388acc590da0
> https://github.com/linux-netdev/nipa/commit/54e060c9094e33bffe356b5d3e25853e22235d49
> to the netdev patchwork checks.
>
> They will likely be pretty noisy so please take them with a grain of
> salt (pretty much like checkpatch). Using the NIPA scripts from the
> commits above could be useful to find the delta of new warnings, since
> there will be quite a few existing ones.
>
> I suspect as we get more experience we will find the warning types to
> disable, and we will drive the number of existing errors down to make
> checking for new ones less of a pain. As I said, for now please don't
> take these checks failing at face value.
This is a possible config for yamllint:
extends: default
rules:
document-start: disable
brackets:
max-spaces-inside: 1
comments:
min-spaces-from-content: 1
line-length:
max: 96
next prev parent reply other threads:[~2025-06-04 9:49 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 [this message]
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
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=m2ldq7vo79.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=kuba@kernel.org \
--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).