linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: linux-kernel@vger.kernel.org,
	Prabhakar <prabhakar.csengg@gmail.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>, Mark Brown <broonie@kernel.org>,
	linux-renesas-soc@vger.kernel.org,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH 1/2] dt-bindings: spi: renesas,rspi: Add r8a7742 to the compatible list
Date: Mon, 24 Aug 2020 17:25:00 -0600	[thread overview]
Message-ID: <20200824232500.GA3531166@bogus> (raw)
In-Reply-To: <20200812150048.27721-2-prabhakar.mahadev-lad.rj@bp.renesas.com>

On Wed, 12 Aug 2020 16:00:47 +0100, Lad Prabhakar wrote:
> Document RZ/G1H (R8A7742) SoC specific bindings. The R8A7742 qspi module
> is identical to R-Car Gen2 family.
> 
> No driver change is needed due to the fallback compatible value
> "renesas,qspi".
> 
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>
> ---
>  Documentation/devicetree/bindings/spi/renesas,rspi.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2020-08-24 23:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 15:00 [PATCH 0/2] r8a7742 add QSPI support Lad Prabhakar
2020-08-12 15:00 ` [PATCH 1/2] dt-bindings: spi: renesas,rspi: Add r8a7742 to the compatible list Lad Prabhakar
2020-08-13  9:21   ` Geert Uytterhoeven
2020-08-24 23:25   ` Rob Herring [this message]
2020-08-12 15:00 ` [PATCH 2/2] ARM: dts: r8a7742: Add QSPI support Lad Prabhakar
2020-08-13  9:24   ` Geert Uytterhoeven
2020-08-18 16:57 ` [PATCH 0/2] r8a7742 add " Mark Brown

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=20200824232500.GA3531166@bogus \
    --to=robh@kernel.org \
    --cc=Chris.Paterson2@renesas.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --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).