[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m24iwuv9wt.fsf@gmail.com>
Date: Thu, 05 Jun 2025 10:02:10 +0100
From: Donald Hunter <donald.hunter@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [ANN] pylint and shellcheck
Jakub Kicinski <kuba@...nel.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
Powered by blists - more mailing lists