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 6/7] arm64: tegra: Device tree changes for v7.1-rc1
Date: Tue, 31 Mar 2026 11:35:28 +0200 [thread overview]
Message-ID: <75edde3a-6ebd-41ea-87ac-468b807593c0@kernel.org> (raw)
In-Reply-To: <acuE-URAuRvmtd4u@orome>
On 31/03/2026 10:43, Thierry Reding wrote:
>>>> Maybe they had more time for previous versions, but
>>>> nevertheless it is also part of other patchset, so it will get into the
>>>> kernel other tree and nothing on v3 posting:
>>>> https://lore.kernel.org/all/20260326135855.2795149-4-thierry.reding@kernel.org/
>>>> gives hints that there will be cross tree merge.
>>>
>>> Maybe look at the cover letter:
>>>
>>> https://lore.kernel.org/all/20260326135855.2795149-1-thierry.reding@kernel.org/
>>>
>>> I clearly pointed out the build dependencies and suggested a shared
>>> branch to resolve them in both trees. Given that the bindings were
>>
>> No problem, that's a valid solution. Can you point me with a lore link
>> to the shared branch posting (these tags/pull requests must be posted on
>> the lists)? Or to an ack from PCI maintainers?
>>
>> The commit itself does not have an Ack, but maybe was just missed.
>
> Yes, the DT bindings patch does not have an Acked-by, but again, I
> didn't think that was necessary, especially since we were going to have
> a cross-merge anyway.
>
> Here's the PR for PCI:
>
> https://lore.kernel.org/linux-tegra/20260329155040.1448158-1-thierry.reding@kernel.org/
Thanks, this solves my question. A note in the pull message (not
necessarily in the tag) would also solve it, BTW.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-31 9:35 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 [this message]
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=75edde3a-6ebd-41ea-87ac-468b807593c0@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