linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH LOCAL] arm64: dts: renesas: r8a774a1: Add required model to dummy board DTS
Date: Thu, 7 Feb 2019 11:42:49 +0100	[thread overview]
Message-ID: <20190207104249.yewajvpwhfoz644l@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWD3x8ZJy_8r1yA4QGAerySjwSAPDESEQwgsyPYscWueg@mail.gmail.com>

On Thu, Feb 07, 2019 at 11:25:24AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Thu, Feb 7, 2019 at 11:14 AM Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Feb 07, 2019 at 10:10:47AM +0100, Geert Uytterhoeven wrote:
> > > make dtbs_check:
> > >
> > >     arch/arm64/boot/dts/renesas/r8a774a1-dummy.dt.yaml: 'model' is a required property
> > >
> > > Fixes: caf23540a44f1036 ("arm64: dts: renesas: r8a774a1: Add dummy board DTS")
> > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > Thanks, applied to topic/arm64-dummy-boards which is included in devel
> > branch of the renesas tree but is not included not the next branch of the
> > renesas tree nor targeted at linux-next.
> 
> Thanks!
> 
> Feel free to squash it into the original, if you think that makes sense.

Thanks, I've left it separate for now.

      reply	other threads:[~2019-02-07 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07  9:10 [PATCH LOCAL] arm64: dts: renesas: r8a774a1: Add required model to dummy board DTS Geert Uytterhoeven
2019-02-07 10:14 ` Simon Horman
2019-02-07 10:25   ` Geert Uytterhoeven
2019-02-07 10:42     ` Simon Horman [this message]

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=20190207104249.yewajvpwhfoz644l@verge.net.au \
    --to=horms@verge.net.au \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --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).