From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Rob Herring <robh@kernel.org>, Daniel Baluta <daniel.baluta@nxp.com>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Julia Lawall" <julia.lawall@inria.fr>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
"Péter Ujfalusi" <peter.ujfalusi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: DT schema bindings conversion mentorships (was Re: [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema)
Date: Thu, 23 May 2024 18:31:32 +0200 [thread overview]
Message-ID: <865295e7-30c8-4abf-9992-fcb9b3186ebb@gmail.com> (raw)
In-Reply-To: <CAL_JsqJp133hGSkja9tabtsE9D7MSA9JErVkmkcy91piHMgfwg@mail.gmail.com>
On 23/05/2024 18:24, Rob Herring wrote:
> On Thu, May 23, 2024 at 7:30 AM Daniel Baluta <daniel.baluta@nxp.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
Thank you Rob, I forwarded your recommendations to the LFX mentees.
Best regards,
Javier Carrasco
next prev parent reply other threads:[~2024-05-23 16:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 7:52 [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema Mighty
2024-05-22 8:42 ` Krzysztof Kozlowski
2024-05-22 13:46 ` Mithil
2024-05-22 14:15 ` Krzysztof Kozlowski
2024-05-22 13:56 ` Péter Ujfalusi
2024-05-22 14:16 ` Krzysztof Kozlowski
2024-05-22 14:43 ` Péter Ujfalusi
2024-05-22 15:22 ` Krzysztof Kozlowski
2024-05-22 16:01 ` Péter Ujfalusi
2024-05-22 16:42 ` Krzysztof Kozlowski
2024-05-22 17:02 ` Mithil
2024-05-22 17:07 ` Mithil
2024-05-22 17:07 ` Krzysztof Kozlowski
2024-05-22 17:30 ` Mithil
2024-05-22 17:47 ` Mithil
2024-05-22 18:49 ` Péter Ujfalusi
2024-05-22 18:39 ` Péter Ujfalusi
2024-05-23 6:08 ` Krzysztof Kozlowski
2024-05-22 17:05 ` DT schema bindings conversion mentorships (was Re: [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema) Krzysztof Kozlowski
2024-05-22 17:47 ` Javier Carrasco
2024-05-23 6:12 ` Krzysztof Kozlowski
2024-05-22 18:36 ` Conor Dooley
2024-05-23 12:33 ` Daniel Baluta
2024-05-23 12:30 ` Daniel Baluta
2024-05-23 16:24 ` Rob Herring
2024-05-23 16:31 ` Javier Carrasco [this message]
2024-05-22 14:22 ` [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema Rob Herring
2024-05-22 14:39 ` Péter Ujfalusi
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=865295e7-30c8-4abf-9992-fcb9b3186ebb@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=julia.lawall@inria.fr \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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).