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: Thu, 05 Jun 2025 10:02:10 +0100 [thread overview]
Message-ID: <m24iwuv9wt.fsf@gmail.com> (raw)
In-Reply-To: <20250604164343.0b71d1ed@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> On Wed, 04 Jun 2025 10:41:14 +0100 Donald Hunter wrote:
>> 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
>
> This fits our current style pretty nicely!
>
> One concern I have is that yamllint walks down the filesystem
> CWD down to root or home dir. So if we put this in
> Documentation/netlink/.yamllint people running yamllint from main dir:
>
> $ yamllint Documentation/netlink/specs/netdev.yaml
>
> will be given incorrect warnings, no? Is there a workaround?
I don't see a workaround without some kind of wrapper.
Maybe just add a makefile? Looks like that was the approach taken for
Documentation/devicetree/bindings
next prev parent reply other threads:[~2025-06-05 9:02 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 [this message]
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=m24iwuv9wt.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 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.