From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [PATCH 3/3] arm64: Add Renesas R8A774B1 support
Date: Mon, 9 Sep 2019 14:30:48 +0200 [thread overview]
Message-ID: <CAMuHMdXxFEmuGRzYJCgqo5EpcXVzt6ZVpsy63BjA9fixFc5vtw@mail.gmail.com> (raw)
In-Reply-To: <1567675844-19247-4-git-send-email-biju.das@bp.renesas.com>
On Thu, Sep 5, 2019 at 11:37 AM Biju Das <biju.das@bp.renesas.com> wrote:
> Add configuration option for the RZ/G2N (R8A774B1) SoC.
>
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-devel for v5.5, with the one-line summary
changed to "soc: renesas: Add Renesas R8A774B1 config option".
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
next prev parent reply other threads:[~2019-09-09 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 9:30 [PATCH 0/3] RZ/G2N SoC identification support Biju Das
2019-09-05 9:30 ` [PATCH 1/3] dt-bindings: arm: Document RZ/G2N SoC DT bindings Biju Das
2019-09-09 12:19 ` Geert Uytterhoeven
2019-09-05 9:30 ` [PATCH 2/3] soc: renesas: Identify RZ/G2N Biju Das
2019-09-09 12:29 ` Geert Uytterhoeven
2019-09-05 9:30 ` [PATCH 3/3] arm64: Add Renesas R8A774B1 support Biju Das
2019-09-09 12:30 ` Geert Uytterhoeven [this message]
2019-09-09 12:32 ` Biju Das
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=CAMuHMdXxFEmuGRzYJCgqo5EpcXVzt6ZVpsy63BjA9fixFc5vtw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).