From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-omap <linux-omap@vger.kernel.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 2/2] more dts changes for omaps for v5.1
Date: Fri, 15 Feb 2019 07:47:42 -0800 [thread overview]
Message-ID: <20190215154742.GJ5720@atomide.com> (raw)
In-Reply-To: <CAK8P3a0kZhJppsFzaTZL+PVCDP8BHwiquF6et3=i6MwA8YNpAg@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> [190215 15:44]:
> On Fri, Feb 15, 2019 at 4:21 PM Arnd Bergmann <arnd@arndb.de> wrote:
> During routine checks, I came across these gta04 warnings:
>
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
>
> Can you have a look and send a fix?
Hmm sounds like that's because the branch is based on v5.0-rc1
that is still missing already merged commit 5b90df44fd9b
("ARM: dts: omap3-gta04: Fix graph_port warning").
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-omap <linux-omap@vger.kernel.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 2/2] more dts changes for omaps for v5.1
Date: Fri, 15 Feb 2019 07:47:42 -0800 [thread overview]
Message-ID: <20190215154742.GJ5720@atomide.com> (raw)
In-Reply-To: <CAK8P3a0kZhJppsFzaTZL+PVCDP8BHwiquF6et3=i6MwA8YNpAg@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> [190215 15:44]:
> On Fri, Feb 15, 2019 at 4:21 PM Arnd Bergmann <arnd@arndb.de> wrote:
> During routine checks, I came across these gta04 warnings:
>
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
> ../arch/arm/boot/dts/omap3-gta04.dtsi:757.7-764.4: Warning
> (graph_port): /ocp@68000000/dss@48050000/encoder@48050c00/port: graph
> node unit address error, expected "0"
>
> Can you have a look and send a fix?
Hmm sounds like that's because the branch is based on v5.0-rc1
that is still missing already merged commit 5b90df44fd9b
("ARM: dts: omap3-gta04: Fix graph_port warning").
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-15 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 18:13 [GIT PULL 1/2] defconfig changes for omaps for v5.1 Tony Lindgren
2019-02-14 18:13 ` Tony Lindgren
2019-02-14 18:13 ` [GIT PULL 2/2] more dts " Tony Lindgren
2019-02-15 15:21 ` Arnd Bergmann
2019-02-15 15:21 ` Arnd Bergmann
2019-02-15 15:43 ` Arnd Bergmann
2019-02-15 15:43 ` Arnd Bergmann
2019-02-15 15:47 ` Tony Lindgren [this message]
2019-02-15 15:47 ` Tony Lindgren
2019-02-15 17:23 ` Arnd Bergmann
2019-02-15 17:23 ` Arnd Bergmann
2019-02-15 17:25 ` Tony Lindgren
2019-02-15 17:25 ` Tony Lindgren
2019-02-15 15:46 ` [GIT PULL 1/2] defconfig " Arnd Bergmann
2019-02-15 15:46 ` Arnd Bergmann
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=20190215154742.GJ5720@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.