From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Biju Das <biju.das@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Chris Paterson <chris.paterson2@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH LOCAL 0/2] arm64: dts: renesas: Add dummy board files
Date: Wed, 23 Jan 2019 13:08:42 +0100 [thread overview]
Message-ID: <CAMuHMdXc+wYJUWy763QOmR4G1-foHZ3v=ua5vYe6hkAi5EEB3A@mail.gmail.com> (raw)
In-Reply-To: <20190123114118.hgwd7uwi7blpgmwl@verge.net.au>
Hi Simon,
On Wed, Jan 23, 2019 at 12:41 PM Simon Horman <horms@verge.net.au> wrote:
> On Fri, Jan 04, 2019 at 10:47:13AM +0100, Simon Horman wrote:
> > On Fri, Jan 04, 2019 at 10:13:14AM +0100, Geert Uytterhoeven wrote:
> > > This patch series adds dummy board files for SoCs that do not have
> > > upstream board support yet (RZ/G2M and RZ/G2E).
> > >
> > > Not intended for upstream merge, but perhaps useful to add to your
> > > topic/renesas-defconfig branch (or a new branch), and merge into devel,
> > > to improve build coverage?
> > >
> > > Thanks!
> > >
> > > Geert Uytterhoeven (2):
> > > [LOCAL] arm64: dts: renesas: r8a774a1: Add dummy board DTS
> > > [LOCAL] arm64: dts: renesas: r8a774c0: Add dummy board DTS
> > >
> > > arch/arm64/boot/dts/renesas/Makefile | 4 ++++
> > > arch/arm64/boot/dts/renesas/r8a774a1-dummy.dts | 2 ++
> > > arch/arm64/boot/dts/renesas/r8a774c0-dummy.dts | 2 ++
> > > 3 files changed, 8 insertions(+)
> > > create mode 100644 arch/arm64/boot/dts/renesas/r8a774a1-dummy.dts
> > > create mode 100644 arch/arm64/boot/dts/renesas/r8a774c0-dummy.dts
> >
> > Thanks, I will create topic/arm64-dummy-boards for these patches
> > and included in the devel branch.
>
> The following files are now present in my tree,
> queued up for v5.0.
>
> arch/arm64/boot/dts/renesas/r8a774c0-cat874.dts
> arch/arm64/boot/dts/renesas/r8a774c0-ek874.dts
>
> Shall I go ahead and drop arch/arm64/boot/dts/renesas/r8a774c0-dummy.dts ?
Yes please, thanks!
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-01-23 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 9:13 [PATCH LOCAL 0/2] arm64: dts: renesas: Add dummy board files Geert Uytterhoeven
2019-01-04 9:13 ` [PATCH LOCAL 1/2] arm64: dts: renesas: r8a774a1: Add dummy board DTS Geert Uytterhoeven
2019-01-09 11:37 ` Fabrizio Castro
2019-01-04 9:13 ` [PATCH LOCAL 2/2] arm64: dts: renesas: r8a774c0: " Geert Uytterhoeven
2019-01-09 11:37 ` Fabrizio Castro
2019-01-04 9:47 ` [PATCH LOCAL 0/2] arm64: dts: renesas: Add dummy board files Simon Horman
2019-01-23 11:41 ` Simon Horman
2019-01-23 12:08 ` Geert Uytterhoeven [this message]
2019-01-24 9:59 ` Simon Horman
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='CAMuHMdXc+wYJUWy763QOmR4G1-foHZ3v=ua5vYe6hkAi5EEB3A@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=biju.das@bp.renesas.com \
--cc=chris.paterson2@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).