public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: arm@kernel.org, soc@kernel.org,
	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 4/7] ARM: tegra: Device tree changes for v7.1-rc1
Date: Tue, 31 Mar 2026 09:42:01 +0200	[thread overview]
Message-ID: <0a94419d-b03e-4c8e-bd49-4a33ce6a8fd7@kernel.org> (raw)
In-Reply-To: <act5kGG-4mZl0j3p@orome>

On 31/03/2026 09:38, Thierry Reding wrote:
>> Why does the DTS branch has mach code? Tag message mentions legacy
>> cleanup only and such cleanup should not cause mixing independent
>> hardware description (DTS) with drivers.
> 
> The DT additions for PAZ00 replace the legacy code, so it makes sense to
> replace it in one patch, otherwise we'd be introducing a bisectability
> problem.

OK, please mention it in the tag message in the future.

Best regards,
Krzysztof


  reply	other threads:[~2026-03-31  7:42 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 [this message]
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
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=0a94419d-b03e-4c8e-bd49-4a33ce6a8fd7@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