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/4] arm64: renesas_defconfig: enable R8A774B1 SoC
Date: Fri, 27 Sep 2019 13:38:59 +0200 [thread overview]
Message-ID: <CAMuHMdXd=Jzmz-k4KrXF=ov=YqGtGmPBkxCCGDs_tFC76+cY_Q@mail.gmail.com> (raw)
In-Reply-To: <1568725530-55241-4-git-send-email-biju.das@bp.renesas.com>
On Tue, Sep 17, 2019 at 3:12 PM Biju Das <biju.das@bp.renesas.com> wrote:
> Enable the Renesas RZ/G2N (R8A774B1) SoC in the ARM64 renesas_defconfig.
>
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will apply to the topic/renesas-defconfig branch, which is not intended
for upstream merge.
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-27 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 13:05 [PATCH 0/4] Add HiHope RZ/G2N main board support Biju Das
2019-09-17 13:05 ` [PATCH 1/4] arm64: dts: renesas: Initial r8a774b1 SoC device tree Biju Das
2019-09-27 12:06 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 2/4] arm64: defconfig: enable R8A774B1 SoC Biju Das
2019-09-27 11:32 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 3/4] arm64: renesas_defconfig: " Biju Das
2019-09-27 11:38 ` Geert Uytterhoeven [this message]
2019-09-17 13:05 ` [PATCH 4/4] arm64: dts: renesas: Add HiHope RZ/G2N main board support Biju Das
2019-09-27 12:38 ` Geert Uytterhoeven
2019-09-27 12:56 ` Biju Das
2019-09-27 13:41 ` 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='CAMuHMdXd=Jzmz-k4KrXF=ov=YqGtGmPBkxCCGDs_tFC76+cY_Q@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).