All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Adam Ford <aford173@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org, aford@beaconembedded.com,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: r8a774e1-beacon-rzg2h-kit: Sync aliases with rz/g2m
Date: Wed, 25 Jan 2023 14:11:07 +0100	[thread overview]
Message-ID: <CAMuHMdUnstJNjkKgD=fPXvCUjqbGZhtwciSF+RrN9RzA2yGUWg@mail.gmail.com> (raw)
In-Reply-To: <20230117232609.477247-2-aford173@gmail.com>

On Wed, Jan 18, 2023 at 1:16 AM Adam Ford <aford173@gmail.com> wrote:
> The Beacon Embedded RZ/G2[MNH] boards all have the same baseboard
> and all share the same PCB.  To make sure all instances appear
> the same, make the aliases for RZ/G2H match the RZ/G2M to
> keep them consistent.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-devel for v6.3.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2023-01-25 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 23:26 [PATCH 1/2] arm64: dts: r8a774b1-beacon-rzg2n-kit: Sync aliases with rz/g2m Adam Ford
2023-01-17 23:26 ` [PATCH 2/2] arm64: dts: r8a774e1-beacon-rzg2h-kit: " Adam Ford
2023-01-25 13:11   ` Geert Uytterhoeven [this message]
2023-01-25 13:10 ` [PATCH 1/2] arm64: dts: r8a774b1-beacon-rzg2n-kit: " Geert Uytterhoeven

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='CAMuHMdUnstJNjkKgD=fPXvCUjqbGZhtwciSF+RrN9RzA2yGUWg@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=aford173@gmail.com \
    --cc=aford@beaconembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.