linux-kernel - Re: DT schema bindings conversion mentorships (was Re: [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema)

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: Windows password security audit tool. GUI, reports in PDF.

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

Date: Thu, 23 May 2024 11:24:51 -0500
From: Rob Herring <robh@...nel.org>
To: Daniel Baluta <daniel.baluta@....com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Shuah Khan <skhan@...uxfoundation.org>, 
	Julia Lawall <julia.lawall@...ia.fr>, Javier Carrasco <javier.carrasco.cruz@...il.com>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org, 
	Péter Ujfalusi <peter.ujfalusi@...il.com>, 
	linux-kernel@...r.kernel.org
Subject: Re: DT schema bindings conversion mentorships (was Re: [PATCH v5]
 ASoC: dt-bindings: omap-mcpdm: Convert to DT schema)

On Thu, May 23, 2024 at 7:30 AM Daniel Baluta <daniel.baluta@....com> wrote:
>
>
> On 5/22/24 20:05, Krzysztof Kozlowski wrote:
> > Dear Daniel, Shuah, Julia, Javier and other mentorship managers,
> >
> > I see some contributions regarding Devicetree bindings which look like
> > efforts of some mentorship programs. It's great, I really like it. Only
> > sadness is that no one ever asked us, Devicetree maintainers, about some
> > sort of guidelines. This leads to sub-optimal allocation of tasks and
> > quite a strain on reviewers side: for example we receive contributions
> > which were never tested (tested as in make target - make
> > dt_binding_check). Or people converted bindings which really do not
> > matter thus their work soon will become obsolete.
> >
>
> Hi Krzysztof,
>
> Some of the faulty patches are on me! Sorry for that. We had an
> unexpected high
>
> number of people sending contributions for Google Summer of Code and I
> couldn't watch them all.
>
> Now, the application period has ended and we have 1 intern working for
> the summer!
>
> Will follow your guidance! Thanks a lot for your help!

To be specific, there are several ways to prioritize what to work on.

- There's a list maintained in CI of number of occurrences of
undocumented (by schema) compatibles[1]. Start at the top.
- Pick a platform (or family of platform) and get the warnings down to
0 or close. There's a grouping of warnings and undocumented
compatibles by platform family at the same link.
- Prioritize newer platforms over older (arm64 rather than
arm32(though there's still new arm32 stuff)).
- Fix warnings treewide from common schemas (i.e. from dtschema).
That's not conversions, but related.

Rob

[1] https://gitlab.com/robherring/linux-dt/-/jobs/6918723853