From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Prabhakar <prabhakar.csengg@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
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,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH] dt-bindings: iio: adc: renesas,rzg2l-adc: Document RZ/Five SoC
Date: Wed, 23 Nov 2022 21:01:47 +0000 [thread overview]
Message-ID: <20221123210147.0bf34345@jic23-huawei> (raw)
In-Reply-To: <166863468321.1016692.3662033617872440170.robh@kernel.org>
On Wed, 16 Nov 2022 15:38:03 -0600
Rob Herring <robh@kernel.org> wrote:
> On Tue, 15 Nov 2022 12:41:28 +0000, Prabhakar wrote:
> > From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> >
> > The ADC block on the RZ/Five SoC is identical to one found on the RZ/G2UL
> > SoC. "renesas,r9a07g043-adc" compatible string will be used on the RZ/Five
> > SoC so to make this clear, update the comment to include RZ/Five SoC.
> >
> > No driver changes are required as generic compatible string
> > "renesas,rzg2l-adc" will be used as a fallback on RZ/Five SoC.
> >
> > Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > ---
> > .../devicetree/bindings/iio/adc/renesas,rzg2l-adc.yaml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
>
> Acked-by: Rob Herring <robh@kernel.org>
Applied. Thanks,
prev parent reply other threads:[~2022-11-23 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:41 [PATCH] dt-bindings: iio: adc: renesas,rzg2l-adc: Document RZ/Five SoC Prabhakar
2022-11-15 12:55 ` Geert Uytterhoeven
2022-11-16 21:38 ` Rob Herring
2022-11-23 21:01 ` 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=20221123210147.0bf34345@jic23-huawei \
--to=jic23@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--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).