The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Maxwell Doose <m32285159@gmail.com>
To: Avermoal <avermoal@gmail.com>
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>,
	"Krzysztof Kozlowski" <krzk+dt@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, 5 Jul 2026 10:04:00 -0500	[thread overview]
Message-ID: <20260705100400.402a91a2@linuxescape> (raw)
In-Reply-To: <20260705085308.8819-2-avermoal@gmail.com>

Hi there,

Firstly, please wait around 24hrs before sending a new version and
additionally mark it with [PATCH vX] (where X is the version of the
patch you're sending, which in this case appears to be 2).

On Sun,  5 Jul 2026 14:53:08 +0600
Avermoal <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.
> 
> The new xilinx-xadc.yaml file was created from the original .txt and
> includes all necessary properties, descriptions, and examples. The
> conversion also fixes a minor typo in the 'xlnx,channels' property name.
> 
> Signed-off-by: Avermoal <avermoal@gmail.com>

Sign off with your real name (or a known identity) to comply with the
DCO.

> ---
>  .../bindings/iio/adc/xilinx-xadc.txt          | 141 -------------
>  .../bindings/iio/adc/xilinx-xadc.yaml         | 186 ++++++++++++++++++
>  2 files changed, 186 insertions(+), 141 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
>  create mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
> 
[snip]
> -- 
>
> Changes in v2:
> - Fix conditional requirement for xlnx,external-mux-channel (add
> if/required block)
> - Correct reg type in child nodes (use maxItems: 1 instead of items)
> - Make #address-cells and #size-cells required under xlnx,channels

Also put this at the top under the ---, it's very difficult to scroll
all the way down here to read it.

-- 
best regards,
max

  reply	other threads:[~2026-07-05 15:04 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 [this message]
2026-07-05 15:42 ` Krzysztof Kozlowski
2026-07-05 16:56   ` Mikhail Lukianchikov
2026-07-05 17:44     ` Maxwell Doose
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=20260705100400.402a91a2@linuxescape \
    --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