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 1/7] dt-bindings: Changes for v7.1-rc1
Date: Mon, 30 Mar 2026 13:39:49 +0200 [thread overview]
Message-ID: <406ca5ed-4a3e-48ba-94ad-d88c53b09299@kernel.org> (raw)
In-Reply-To: <20260329151045.1443133-1-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)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-dt-bindings
>
> for you to fetch changes up to bed2f5b4de6c6fd8f8928f6373ad92e8795c370f:
>
> dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit (2026-03-28 01:05:24 +0100)
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> dt-bindings: Changes for v7.1-rc1
>
> This contains a few conversions to DT schema along with various
> additions and fixes to reduce the amount of validation warnings.
>
> Included are also a new binding for the PCIe controller found on
> Tegra264 as well as compatible strings for the Jetson AGX Thor
> Developer Kit.
>
> ----------------------------------------------------------------
> Sumit Gupta (1):
> dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings
>
> Svyatoslav Ryhel (1):
> dt-bindings: display: tegra: Document Tegra20 HDMI port
>
> Thierry Reding (9):
> dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
Why are you taking subsystem patches? This was posted on 26th of March
and was not acked by PCI maintainers.
How the bindings should go is already documented, so there is no
question here.
The question was whether you can take them if subsystem maintainer is
non-responsive and yes, you can. You gave PCI maintainers one day before
applying it.
> dt-bindings: phy: tegra-xusb: Document Type C support
No acks, but that is waiting for one month so it is fine.
> dt-bindings: clock: tegra124-dfll: Convert to json-schema
> dt-bindings: interrupt-controller: tegra: Fix reg entries
> dt-bindings: arm: tegra: Add missing compatible strings
> dt-bindings: phy: tegra: Document Tegra210 USB PHY
> dt-bindings: memory: Add Tegra210 memory controller bindings
> dt-bindings: memory: tegra210: Mark EMC as cooling device
That's even my subsystem and I did not ack it. You did not even sent it
to me as requested by MAINTAINERS file (+dt is ignore alias), so
obviously I did not even had a chance to ack it.
And we even had few days ago talk were I explained you how these
bindings must go. Seeing pull request completely ignoring that
discussion is just huge surprise.
No, it cannot go in. Send patches to proper maintainers first.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-30 11:39 UTC|newest]
Thread overview: 11+ 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-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-29 15:10 ` [GIT PULL 7/7] arm64: tegra: Default configuration " Thierry Reding
2026-03-30 11:39 ` Krzysztof Kozlowski [this message]
2026-03-30 11:40 ` [GIT PULL 1/7] dt-bindings: Changes " 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=406ca5ed-4a3e-48ba-94ad-d88c53b09299@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