From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ciprian Regus <ciprian.regus@analog.com>,
jic23@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: iio: adc: Add docs for LTC2499
Date: Thu, 1 Sep 2022 16:27:05 +0300 [thread overview]
Message-ID: <05eb3c6a-404d-1bfd-1361-cff952b68400@linaro.org> (raw)
In-Reply-To: <20220901121700.1325733-1-ciprian.regus@analog.com>
On 01/09/2022 15:16, Ciprian Regus wrote:
> Update the bindings documentation for ltc2497 to include the ltc2499.
>
> Signed-off-by: Ciprian Regus <ciprian.regus@analog.com>
> ---
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-01 13:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 12:16 [PATCH v2 1/5] dt-bindings: iio: adc: Add docs for LTC2499 Ciprian Regus
2022-09-01 12:16 ` [PATCH v2 2/5] Add the LTC2496 MAINTAINERS entry Ciprian Regus
2022-09-04 14:54 ` Jonathan Cameron
2022-09-01 12:16 ` [PATCH v2 3/5] Remove duplicate matching entry Ciprian Regus
2022-09-01 12:16 ` [PATCH v2 4/5] drivers: iio: adc: LTC2499 support Ciprian Regus
2022-09-01 13:23 ` Krzysztof Kozlowski
2022-09-02 11:06 ` Jonathan Cameron
2022-09-02 11:37 ` Andy Shevchenko
2022-09-04 14:55 ` Jonathan Cameron
2022-09-05 8:58 ` Krzysztof Kozlowski
2022-09-01 20:00 ` kernel test robot
2022-09-04 15:08 ` Jonathan Cameron
2022-09-01 20:10 ` kernel test robot
2022-09-04 15:06 ` Jonathan Cameron
2022-09-01 12:17 ` [PATCH v2 5/5] drivers: iio: adc: Rename the LTC2499 iio device Ciprian Regus
2022-09-04 15:09 ` Jonathan Cameron
2022-09-01 13:27 ` Krzysztof Kozlowski [this message]
2022-09-04 14:53 ` [PATCH v2 1/5] dt-bindings: iio: adc: Add docs for LTC2499 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=05eb3c6a-404d-1bfd-1361-cff952b68400@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=ciprian.regus@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).