From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: r8a7795-es1: Drop extra zero from usb unit address
Date: Fri, 18 Aug 2017 10:07:26 +0200 [thread overview]
Message-ID: <CAMuHMdVrtWBYEgS5Wapn_oyg2izuOkGzSdX-hXmMn8C2iJaJXQ@mail.gmail.com> (raw)
In-Reply-To: <20170818080215.GG9175@verge.net.au>
Hi Simon,
On Fri, Aug 18, 2017 at 10:02 AM, Simon Horman <horms@verge.net.au> wrote:
> On Thu, Aug 17, 2017 at 01:29:14PM +0200, Geert Uytterhoeven wrote:
>> With W=1:
>>
>> arch/arm64/boot/dts/renesas/r8a7795-es1-salvator-x.dtb: Warning (simple_bus_reg): Node /soc/usb at ee0400000 simple-bus unit address format error, expected "ee040000"
>> arch/arm64/boot/dts/renesas/r8a7795-es1-h3ulcb.dtb: Warning (simple_bus_reg): Node /soc/usb at ee0400000 simple-bus unit address format error, expected "ee040000"
>>
>> Fixes: 291e0c4994d0813f ("arm64: dts: r8a7795: Add support for R-Car H3 ES2.0")
>> Fixes: 171f2ef82284f61b ("arm64: dts: r8a7795: Add USB3.0 host device nodes")
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> ---
>> The second fixes tag is for the original r8a7795.dtsi, before
>> r8a7795-es1.dtsi was split off.
>
> Do you want this treated as a fix for v4.13 or v4.14, or a regular patch
> for v4.15? It looks like the problem has been present in some form since
> v4.12.
It's not a critical fix (no impact at all?), so v4.15 is fine.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at 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:[~2017-08-18 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 11:29 [PATCH] arm64: dts: r8a7795-es1: Drop extra zero from usb unit address Geert Uytterhoeven
2017-08-18 8:02 ` Simon Horman
2017-08-18 8:07 ` Geert Uytterhoeven [this message]
2017-08-21 8:56 ` 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=CAMuHMdVrtWBYEgS5Wapn_oyg2izuOkGzSdX-hXmMn8C2iJaJXQ@mail.gmail.com \
--to=geert@linux-m68k.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).