From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Samuel Holland <samuel@sholland.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: adc: ti,adc081c: Document the binding
Date: Sat, 3 Dec 2022 17:41:25 +0000 [thread overview]
Message-ID: <20221203174125.28e1bfbf@jic23-huawei> (raw)
In-Reply-To: <ef692f82-61c3-b812-b846-64bde04c8bb3@linaro.org>
On Sun, 27 Nov 2022 22:09:52 +0100
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 25/11/2022 23:09, Samuel Holland wrote:
> > Linux has a driver for these ADCs at drivers/iio/adc/ti-adc081c.c, but
> > the compatible strings were undocumented. Add a binding for them. The
> > hardware has an alert interrupt output, but existing ti,adc081c users
> > do not provide the 'interrupts' property, so leave it as optional.
> >
> > Signed-off-by: Samuel Holland <samuel@sholland.org>
> > ---
> >
>
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Applied, but now we are so close to merge window, I'm queuing things
for 6.3. Obviously wouldn't really matter for this, but it is too
late for other things in my tree to get enough time in linux-next
etc.
Jonathan
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2022-12-03 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 22:09 [PATCH] dt-bindings: iio: adc: ti,adc081c: Document the binding Samuel Holland
2022-11-27 12:51 ` Krzysztof Kozlowski
2022-11-27 17:42 ` Jonathan Cameron
2022-11-27 18:01 ` Samuel Holland
2022-11-27 21:08 ` Krzysztof Kozlowski
2022-11-27 21:09 ` Krzysztof Kozlowski
2022-11-27 21:09 ` Krzysztof Kozlowski
2022-12-03 17:41 ` 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=20221203174125.28e1bfbf@jic23-huawei \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.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).