public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	Chris Brandt <chris.brandt@renesas.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-kernel@vger.kernel.org,
	Prabhakar <prabhakar.csengg@gmail.com>,
	Biju Das <biju.das.jz@bp.renesas.com>,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: i2c: renesas,riic: Document RZ/V2L SoC
Date: Wed, 2 Mar 2022 12:24:15 -0600	[thread overview]
Message-ID: <Yh+2T/Mny15X+pOq@robh.at.kernel.org> (raw)
In-Reply-To: <20220301125046.17737-1-prabhakar.mahadev-lad.rj@bp.renesas.com>

On Tue, Mar 01, 2022 at 12:50:46PM +0000, Lad Prabhakar wrote:
> Document RZ/V2L I2C bindings. RZ/V2L I2C is identical to one found on the
> RZ/G2L and RZ/A SoC's. No driver changes are required as the generic
> compatible string "renesas,riic-rz" will be used as a fallback.
> 
> While at it, drop the comment "# RZ/A or RZ/G2L" for "renesas,riic-rz"
> compatible string as this will avoid changing the line for every new
> SoC addition.
> 
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Reviewed-by: Biju Das <biju.das.jz@bp.renesas.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v1->v2
> * Included Ack and RB tags
> * Dropped the comment from generic string as suggested by Geert.
> 
> v1:
> https://patchwork.kernel.org/project/linux-renesas-soc/patch/
> 20220227214747.24819-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
> ---
>  Documentation/devicetree/bindings/i2c/renesas,riic.yaml | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)

I already applied v1. I may have missed this because PW stopped getting 
mail the last 2 days.

Rob

  parent reply	other threads:[~2022-03-02 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 12:50 [PATCH v2] dt-bindings: i2c: renesas,riic: Document RZ/V2L SoC Lad Prabhakar
2022-03-01 16:32 ` Wolfram Sang
2022-03-02 18:24 ` Rob Herring [this message]
2022-03-02 21:08   ` Wolfram Sang

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=Yh+2T/Mny15X+pOq@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=chris.brandt@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-i2c@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=wsa+renesas@sang-engineering.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