linux-kernel - Re: [PATCH 05/18] MIPS: DTS: jz4780: fix pinctrl as reported by dtbscheck

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <499848FD-3F64-4B5D-9259-5C9E1ED4E8AB@goldelico.com>
Date:   Sat, 9 Apr 2022 15:41:37 +0200
From:   "H. Nikolaus Schaller" <hns@...delico.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Paul Cercueil <paul@...pouillou.net>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        linux-mips@...r.kernel.org, letux-kernel@...nphoenux.org
Subject: Re: [PATCH 05/18] MIPS: DTS: jz4780: fix pinctrl as reported by
 dtbscheck



> Am 09.04.2022 um 15:24 schrieb Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>:
> 
> On 09/04/2022 15:22, H. Nikolaus Schaller wrote:
>>> 
>>> What does that mean? One cannot create multiple patches and apply them?
>> 
>> This patch set was created by some automatic scripts. And they produce one patch
>> per group of warnings.
>> 
>> But here you ask me to merge 4 unrelated topics into a single one.
>> 
>> Or do you mean something else?
> 
> You can edit a commit, right? git commit --amend? So where is the problem?

It is not about capabilites...

It is about understanding why you want it and what you expect.

> 
>> 
>>> 
>>>> And they are not related. Every one is based on a different .yaml
>>>> schema file.
>>> 
>>> Which does not matter, because the name of the node does not matter. We
>>> enforce it in schema to makes things organized and easier in testing.
>>> This does not fix any real problem, just the problem we created by
>>> ourselves with schema.
>>> 
>>>> 
>>>> That in all cases the result looks similar comes from similar
>>>> requirements by the schemata and has no inherent connection.
>>> 
>>> All schemas will require it, won't they? The same for arm...
>> 
>> We may be talking about different things here.
>> 
>> My understanding:
>> you ask me to merge 5/18, 8/18, 9/18, 12/18 because they contain "controller" in the node-name.
>> 
>> Right? If not then we must clarify that first.
> 
> No. I ask you to fix all pin-controller cases, for entire MIPS, not just
> one.

Oops. Nope. I am a volunteer and neither your employee nor slave.

> And in one month one more. And then again one more.

No. I work for the topics I choose to work on and share the results.
Open source lives from taking and giving...

If you want me to contribute, please be not demanding.

BR and thanks,
Nikolaus