From: baolin.wang@linaro.org (Baolin Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: sprd: fix typo in 'remote-endpoint'
Date: Thu, 24 May 2018 13:27:13 +0800 [thread overview]
Message-ID: <CAMz4kuKVknMt578MGCnP_wzLB_o-yttHXD9uxbFBDXYq6XiTRQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKrsTpgnLfxhcxeucpoh9NkyGwwZq82QUBgJZrdjGYQzg@mail.gmail.com>
On 24 May 2018 at 04:30, Rob Herring <robh@kernel.org> wrote:
> On Tue, May 8, 2018 at 8:58 PM, Chunyan Zhang <zhang.lyra@gmail.com> wrote:
>> Hi Rob,
>>
>> On 8 May 2018 at 23:09, Rob Herring <robh@kernel.org> wrote:
>>> dtc now warns on incomplete OF graph endpoint connections:
>>>
>>> arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: Warning (graph_endpoint): /soc/stm at 10006000/port/endpoint: graph connection to node '/soc/funnel at 10001000/ports/port at 2/endpoint' is not bidirectional
>>>
>>> The cause is a typo in 'remote-endpoint'.
>>
>> Thanks for fixing this and,
>>
>> Acked-by: Chunyan Zhang <zhang.lyra@gmail.com>
>
> Is someone going to apply this? Still seeing warnings in linux-next.
I think Arnd will pick up this patch.
--
Baolin.wang
Best Regards
next prev parent reply other threads:[~2018-05-24 5:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 15:09 [PATCH] arm64: dts: juno: fix OF graph endpoint node names Rob Herring
2018-05-08 15:09 ` [PATCH] arm64: dts: juno: fix missing Coresight STM graph connection Rob Herring
2018-05-08 15:09 ` [PATCH] arm64: dts: msm8916: fix Coresight ETF graph connections Rob Herring
2018-05-23 20:29 ` Rob Herring
2018-05-24 4:48 ` Ivan T. Ivanov
2018-05-24 16:32 ` Mathieu Poirier
2018-05-25 22:46 ` Andy Gross
2018-05-08 15:09 ` [PATCH] arm64: dts: sprd: fix typo in 'remote-endpoint' Rob Herring
2018-05-09 1:58 ` Chunyan Zhang
2018-05-23 20:30 ` Rob Herring
2018-05-24 5:27 ` Baolin Wang [this message]
2018-05-25 2:36 ` Chunyan Zhang
2018-05-25 22:11 ` Olof Johansson
2018-05-08 15:15 ` [PATCH] arm64: dts: juno: fix OF graph endpoint node names Liviu Dudau
2018-05-09 16:34 ` Sudeep Holla
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=CAMz4kuKVknMt578MGCnP_wzLB_o-yttHXD9uxbFBDXYq6XiTRQ@mail.gmail.com \
--to=baolin.wang@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 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).