From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [GIT PULL] arm64: dts: samsung: Second pull for v5.17
Date: Wed, 19 Jan 2022 15:49:02 +0100 [thread overview]
Message-ID: <495d7eee-ab87-d330-119c-eaafa6c1dee7@canonical.com> (raw)
In-Reply-To: <CAPLW+4=vEYm6dGSCXtmiXUVe7FT6p=6Uk=MCvEsEgcdTz-R0NA@mail.gmail.com>
On 19/01/2022 15:35, Sam Protsenko wrote:
> On Mon, 27 Dec 2021 at 13:30, Krzysztof Kozlowski
> <krzysztof.kozlowski@canonical.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?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-01-19 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 11:29 Krzysztof Kozlowski
2022-01-19 14:35 ` Sam Protsenko
2022-01-19 14:49 ` Krzysztof Kozlowski [this message]
2022-01-19 15:07 ` Sam Protsenko
2022-01-19 15:11 ` Sam Protsenko
2022-01-19 16:06 ` Arnd Bergmann
2022-01-19 16:53 ` Olof Johansson
2022-01-19 17:00 ` Krzysztof Kozlowski
2022-01-19 19:43 ` Olof Johansson
2022-01-22 12:38 ` Sam Protsenko
2022-01-23 19:27 ` Krzysztof Kozlowski
2022-01-24 13:50 ` Sam Protsenko
2022-01-25 13:21 ` Krzysztof Kozlowski
2022-01-27 9:33 ` Krzysztof Kozlowski
2022-01-27 16:58 ` Sam Protsenko
2022-01-28 7:46 ` Krzysztof Kozlowski
2022-01-31 13:15 ` Sam Protsenko
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=495d7eee-ab87-d330-119c-eaafa6c1dee7@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=semen.protsenko@linaro.org \
--cc=soc@kernel.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
all inboxes | Powered by JetHome®