[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPLW+4nM_8nbf4inP2pGMVbkE+OYwbkPrfjKtPAYPBfUXvF32A@mail.gmail.com>
Date: Wed, 19 Jan 2022 17:07:32 +0200
From: Sam Protsenko <semen.protsenko@...aro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc: Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
arm@...nel.org, soc@...nel.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
Krzysztof Kozlowski <krzk@...nel.org>
Subject: Re: [GIT PULL] arm64: dts: samsung: Second pull for v5.17
On Wed, 19 Jan 2022 at 16:49, Krzysztof Kozlowski
<krzysztof.kozlowski@...onical.com> wrote:
>
> On 19/01/2022 15:35, Sam Protsenko wrote:
> > On Mon, 27 Dec 2021 at 13:30, Krzysztof Kozlowski
> > <krzysztof.kozlowski@...onical.com> wrote:
> >>
> >> Hi,
> >>
> >> Second pull with DTS for ARM64, on top of previous pull.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >>
> >> The following changes since commit 51b1a5729469cef57a3c97aa014aa6e1d2b8d864:
> >>
> >> dt-bindings: pinctrl: samsung: Add pin drive definitions for Exynos850 (2021-12-20 10:35:32 +0100)
> >>
> >> are available in the Git repository at:
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt64-5.17-2
> >>
> >> for you to fetch changes up to a1828d772e0738c30a383a7d335aded2f2baf908:
> >>
> >> arm64: dts: exynos: Add initial E850-96 board support (2021-12-22 12:31:13 +0100)
> >>
> >> ----------------------------------------------------------------
> >> Samsung DTS ARM64 changes for v5.17, part two
> >>
> >> Add initial Exynos850 support and WinLink E850-96 board using it.
> >>
> >> ----------------------------------------------------------------
> >> Sam Protsenko (2):
> >> arm64: dts: exynos: Add initial Exynos850 SoC support
> >> arm64: dts: exynos: Add initial E850-96 board support
> >>
> >
> > Hi Krzysztof,
> >
> > Do you know if this series is going to land in v5.17?
>
> I don't know, did not check.
>
> > The prediction
> > (by phb-crystal-ball) is that MW closes on 23 Jan. I can see those
> > patches in soc/for-next [1], but want to be sure those are scheduled
> > for v5.17.
>
> I don't get how can you be sure that they will be in v5.17. If they are
> not going to be pulled - what can you do?
>
I can't. Just haven't seen corresponding pull request to mainline tree
on ML yet, thought you may know something. Basically I just don't want
those patches to be lost accidentally. And of course it'd nice to see
those in v5.17. Anyway, that question should've been probably directed
to Olof and Arnd, sorry for disturbing.
>
> Best regards,
> Krzysztof
Powered by blists - more mailing lists