From: Jonathan Cameron <jic23@kernel.org>
To: Flaviu Nistor <flaviu.nistor@gmail.com>
Cc: David Lechner <dlechner@baylibre.com>,
Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
Antoniu Miclaus <antoniu.miclaus@analog.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: adc: ti,ads1015: Add label property
Date: Sat, 5 Sep 2026 02:54:31 +0100 [thread overview]
Message-ID: <20260905025431.1d1e4d1d@jic23-huawei> (raw)
In-Reply-To: <20260902172230.5234-1-flaviu.nistor@gmail.com>
On Wed, 2 Sep 2026 20:22:29 +0300
Flaviu Nistor <flaviu.nistor@gmail.com> wrote:
> Add support for an optional label property per channel similar to other adc
> chips. This allows assigning distinct names for each channel which can
> match the schematic signal name.
>
> Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>
Please always use a cover letter for multipatch series.
Makes it easier to handle them with tooling and also provides a place
for general comments etc.
prev parent reply other threads:[~2026-09-05 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 17:22 [PATCH v2 1/2] dt-bindings: iio: adc: ti,ads1015: Add label property Flaviu Nistor
2026-09-02 17:22 ` [PATCH v2 2/2] iio: adc: ti-ads1015: Add support for label Flaviu Nistor
2026-09-02 17:40 ` sashiko-bot
2026-09-02 18:37 ` David Lechner
2026-09-03 6:18 ` Andy Shevchenko
2026-09-03 15:16 ` Flaviu Nistor
2026-09-03 15:28 ` David Lechner
2026-09-03 19:03 ` Andy Shevchenko
2026-09-05 2:01 ` Jonathan Cameron
2026-09-02 18:31 ` [PATCH v2 1/2] dt-bindings: iio: adc: ti,ads1015: Add label property David Lechner
2026-09-03 15:19 ` Flaviu Nistor
2026-09-03 15:30 ` David Lechner
2026-09-05 1:56 ` Jonathan Cameron
2026-09-05 1:54 ` Jonathan Cameron [this message]
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=20260905025431.1d1e4d1d@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=flaviu.nistor@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).