linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Rob Herring <robh@kernel.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
	"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	devicetree <devicetree@vger.kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Discussions about the Letux Kernel"
	<letux-kernel@openphoenux.org>
Subject: Re: [PATCH v2] ARM: dts: omap3-gta04: Fix graph_port warning
Date: Wed, 9 Jan 2019 13:39:03 -0800	[thread overview]
Message-ID: <20190109213903.GV5544@atomide.com> (raw)
In-Reply-To: <CAL_JsqLhGGx_amtDSZh3OJ+Tq-Oziu450NOt4Z+aoQMt-JY46Q@mail.gmail.com>

* Rob Herring <robh@kernel.org> [190109 19:38]:
> On Wed, Jan 9, 2019 at 1:02 PM H. Nikolaus Schaller <hns@goldelico.com> wrote:
> >
> > From: Tony Lindgren <tony@atomide.com>
> >
> > We're currently getting a warning with make dtbs:
> >
> > arch/arm/boot/dts/omap3-gta04.dtsi:720.7-727.4: Warning (graph_port):
> > /ocp@68000000/dss@48050000/encoder@48050c0 0/port: graph node unit
> > address error, expected "0"
> >
> > Tested-by: H. Nikolaus Schaller <hns@goldelico.com>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> 
> Acked-by: Rob Herring <robh@kernel.org>

Nikolaus, care to reply with your Signed-off-by since
you also edited the patch?

Regards,

Tony

  reply	other threads:[~2019-01-09 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 19:01 [PATCH v2] ARM: dts: omap3-gta04: Fix graph_port warning H. Nikolaus Schaller
2019-01-09 19:37 ` Rob Herring
2019-01-09 21:39   ` Tony Lindgren [this message]
2019-01-10  5:31     ` H. Nikolaus Schaller
2019-01-10 16:17       ` Tony Lindgren

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=20190109213903.GV5544@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=tomi.valkeinen@ti.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).