From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip dts32 fix for 4.18
Date: Sun, 15 Jul 2018 17:46:09 +0200 [thread overview]
Message-ID: <1884349.WTgIHKSUBb@phil> (raw)
In-Reply-To: <20180714221105.u7gbyetcpjhlylfl@localhost>
Am Sonntag, 15. Juli 2018, 00:11:05 CEST schrieb Olof Johansson:
> On Wed, Jul 11, 2018 at 04:18:55PM +0200, Heiko Stuebner wrote:
> > Hi Arnd, Kevin, Olof,
> >
> > please find below a one-patch pull fixing a new warning the updated dtc
> > in 4.18 found. So far no other regressions have been found in Rockchip
> > parts it seems. So please pull!
> >
> > Thanks
> > Heiko
> >
> > The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
> >
> > Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.18-rockchip-dts32fixes-1
> >
> > for you to fetch changes up to cddb86833615d9550d7b3a1b65b71071784dae70:
> >
> > ARM: dts: rockchip: fix graph node unit address error from dtc (2018-06-17 09:31:34 +0200)
>
> I took the liberty to declare this non-urgent and queued it up with next/dt
> instead for 4.19. It's just a warning and we're past rc4 so it seemed like
> a reasonable call. Let me know if it has actual functional impact/regression
> though.
no problem from my side, it's just dtc emiting the warning :-)
I just saw this the first time with 4.18-rc1, so it seems to stem from
a newer dtc and remembered that previous dtc fixes from Arnd or so
went in as fixes.
Heiko
next prev parent reply other threads:[~2018-07-15 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 14:18 [GIT PULL] Rockchip dts32 fix for 4.18 Heiko Stuebner
2018-07-14 22:11 ` Olof Johansson
2018-07-15 15:46 ` Heiko Stuebner [this message]
2018-07-16 7:26 ` 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=1884349.WTgIHKSUBb@phil \
--to=heiko@sntech.de \
--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).