From: "Maxwell Doose" <m32285159@gmail.com>
To: "Mikhail Lukianchikov" <avermoal@gmail.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Michal Simek" <michal.simek@amd.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
Date: Sun, 05 Jul 2026 12:44:46 -0500 [thread overview]
Message-ID: <DJQTOY88KR1E.1U2393N7KUH12@gmail.com> (raw)
In-Reply-To: <20260705165620.9818-1-avermoal@gmail.com>
On Sun Jul 5, 2026 at 11:56 AM CDT
Mikhail Lukianchikov <avermoal@gmail.com> wrote:
>>> Convert the Xilinx XADC binding documentation from .txt to YAML format.
>>> This conversion is part of the ongoing effort to migrate all DT bindings
>>> to a machine-verifiable schema.
>>
>>Sorry, but what effort exactly? Where is this effort documented? Do you
>>have a mentor if this is some sort of mentorship effort?
>>
>>And if this is ongoing effort then don't duplicate:
>>https://lore.kernel.org/all/?q=dfn%3Axilinx-xadc.txt
>
> Hello Krzyszof,
>
> Thank you for feedback.
>
> I'm the newbie at Linux kernel developers community,
> and sorry for my mistakes in sending commits.
>
No worries, we've all done it at some point. If you're looking for stuff
to do then the todo in drivers/iio/ was just recently updated. There are
still a handful of drivers also in iio that still need conversions to
guard()().
>
> I'll answer your questions.
> I am not part of any official mentorship program,
> I just decided to try to contribute to the development of the Linux kernel.
> Yes, it's a ongoing effort, and to be honest, this effort is the general
> community initiative to convert all DT bindings from .txt to .yaml. I didn't know that work
> on this file was already underway.
>
> Tell me, should I continue working in this case?
>
After looking at the link Krzysztof sent you it looks like it's already
being done, so I'd recommend dropping this one.
--
best regards,
max
next prev parent reply other threads:[~2026-07-05 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 8:53 [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML Avermoal
2026-07-05 15:04 ` Maxwell Doose
2026-07-05 15:42 ` Krzysztof Kozlowski
2026-07-05 16:56 ` Mikhail Lukianchikov
2026-07-05 17:44 ` Maxwell Doose [this message]
2026-07-05 23:04 ` Jonathan Cameron
2026-07-06 5:56 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2026-07-05 6:34 Avermoal
2026-07-05 15:42 ` Krzysztof Kozlowski
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=DJQTOY88KR1E.1U2393N7KUH12@gmail.com \
--to=m32285159@gmail.com \
--cc=andy@kernel.org \
--cc=avermoal@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox