From: Olof Johansson <olof@lixom.net>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip dts32 fix for 4.18
Date: Sat, 14 Jul 2018 15:11:05 -0700 [thread overview]
Message-ID: <20180714221105.u7gbyetcpjhlylfl@localhost> (raw)
In-Reply-To: <1776596.Q4iCTXTKyP@phil>
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.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip dts32 fix for 4.18
Date: Sat, 14 Jul 2018 15:11:05 -0700 [thread overview]
Message-ID: <20180714221105.u7gbyetcpjhlylfl@localhost> (raw)
In-Reply-To: <1776596.Q4iCTXTKyP@phil>
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.
-Olof
next prev parent reply other threads:[~2018-07-14 22:11 UTC|newest]
Thread overview: 8+ 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-11 14:18 ` Heiko Stuebner
2018-07-14 22:11 ` Olof Johansson [this message]
2018-07-14 22:11 ` Olof Johansson
2018-07-15 15:46 ` Heiko Stuebner
2018-07-15 15:46 ` Heiko Stuebner
2018-07-16 7:26 ` Arnd Bergmann
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=20180714221105.u7gbyetcpjhlylfl@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@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 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.