From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>,
Rodrigo Alencar <rodrigo.alencar@analog.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v3 1/6] dt-bindings: iio: frequency: add adf41513
Date: Mon, 12 Jan 2026 17:32:42 +0100 [thread overview]
Message-ID: <48f00a0b-667b-4aa0-93a2-e1045e20e309@kernel.org> (raw)
In-Reply-To: <7ck6vexpeak47kob7niupkdg3nbyvp4nab7rqmz6niq4frf64y@tjnph6hno32z>
On 12/01/2026 11:04, Rodrigo Alencar wrote:
>>
>> One example - more complete, so the next one - is enough. They do not
>> differ.
>>
>
> Not sure I undestood this message:
> - are those examples 'enough' as the second one is 'more complete'?
> - do I need to change the second example to be 'more complete',
> because 'they do not differ'?
> - do I need to create 'one example' 'more complete', apart from the existing ones?
Just have one example, e.g. the second one.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-12 16:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 12:14 [PATCH v3 0/6] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar via B4 Relay
2026-01-08 12:14 ` [PATCH v3 1/6] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar via B4 Relay
2026-01-09 8:13 ` Krzysztof Kozlowski
2026-01-12 10:04 ` Rodrigo Alencar
2026-01-12 16:32 ` Krzysztof Kozlowski [this message]
2026-01-08 12:14 ` [PATCH v3 2/6] iio: frequency: adf41513: driver implementation Rodrigo Alencar via B4 Relay
2026-01-09 18:55 ` Andy Shevchenko
2026-01-12 9:56 ` Rodrigo Alencar
2026-01-12 10:57 ` Andy Shevchenko
2026-01-13 9:32 ` Rodrigo Alencar
2026-01-16 11:31 ` Rodrigo Alencar
2026-01-16 13:50 ` Andy Shevchenko
2026-01-16 13:53 ` Andy Shevchenko
2026-01-11 13:53 ` Jonathan Cameron
2026-01-08 12:14 ` [PATCH v3 3/6] iio: frequency: adf41513: handle LE synchronization feature Rodrigo Alencar via B4 Relay
2026-01-11 13:58 ` Jonathan Cameron
2026-01-08 12:14 ` [PATCH v3 4/6] iio: frequency: adf41513: features on frequency change Rodrigo Alencar via B4 Relay
2026-01-09 19:07 ` Andy Shevchenko
2026-01-12 9:45 ` Rodrigo Alencar
2026-01-12 10:54 ` Andy Shevchenko
2026-01-16 17:57 ` Jonathan Cameron
2026-01-19 7:38 ` Andy Shevchenko
2026-01-19 10:41 ` Jonathan Cameron
2026-01-19 13:18 ` Andy Shevchenko
2026-01-08 12:14 ` [PATCH v3 5/6] docs: iio: add documentation for adf41513 driver Rodrigo Alencar via B4 Relay
2026-01-08 12:14 ` [PATCH v3 6/6] Documentation: ABI: testing: add common ABI file for iio/frequency Rodrigo Alencar via B4 Relay
2026-01-11 14:01 ` Jonathan Cameron
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=48f00a0b-667b-4aa0-93a2-e1045e20e309@kernel.org \
--to=krzk@kernel.org \
--cc=455.rodrigo.alencar@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@analog.com \
/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