From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>,
arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1
Date: Tue, 31 Mar 2026 09:59:07 +0200 [thread overview]
Message-ID: <63b6c9da-4c0e-497c-a2a6-8aa5e74e2adb@kernel.org> (raw)
In-Reply-To: <20260329151045.1443133-6-thierry.reding@kernel.org>
On 29/03/2026 17:10, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
>
> Hi ARM SoC maintainers,
>
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>
> Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>
I guess related to my question why patches were applied one day after
the list:
Days in linux-next:
----------------------------------------
0 | ++++++++ (8)
Commits with 0 days in linux-next (8 of 8: 100.0%):
...
So you exposed soc tree to all sort of integration issues. No, please
keep them for some days in the next before you send them to soc, to
allow people to test and eventually complain/report issues.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-31 7:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 15:10 [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1 Thierry Reding
2026-03-29 15:10 ` [GIT PULL 2/7] soc/tegra: " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 3/7] firmware: tegra: " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 4/7] ARM: tegra: Device tree changes " Thierry Reding
2026-03-30 11:46 ` Krzysztof Kozlowski
2026-03-31 7:38 ` Thierry Reding
2026-03-31 7:42 ` Krzysztof Kozlowski
2026-04-04 14:04 ` Krzysztof Kozlowski
2026-03-29 15:10 ` [GIT PULL 5/7] ARM: tegra: Default configuration " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 6/7] arm64: tegra: Device tree " Thierry Reding
2026-03-30 11:45 ` Krzysztof Kozlowski
2026-03-31 7:53 ` Thierry Reding
2026-03-31 8:00 ` Krzysztof Kozlowski
2026-03-31 8:43 ` Thierry Reding
2026-03-31 9:35 ` Krzysztof Kozlowski
2026-03-31 7:59 ` Krzysztof Kozlowski [this message]
2026-03-31 8:13 ` Thierry Reding
2026-04-02 12:02 ` Thierry Reding
2026-04-03 7:35 ` Krzysztof Kozlowski
2026-03-29 15:10 ` [GIT PULL 7/7] arm64: tegra: Default configuration " Thierry Reding
2026-03-30 11:39 ` [GIT PULL 1/7] dt-bindings: Changes " Krzysztof Kozlowski
2026-03-30 11:40 ` Krzysztof Kozlowski
2026-03-31 8:25 ` Thierry Reding
2026-03-31 9:50 ` Krzysztof Kozlowski
2026-03-31 11:09 ` Thierry Reding
2026-03-31 11:28 ` Krzysztof Kozlowski
2026-04-02 12:00 ` Thierry Reding
2026-04-03 7:39 ` Krzysztof Kozlowski
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=63b6c9da-4c0e-497c-a2a6-8aa5e74e2adb@kernel.org \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=soc@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@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