From: "Arnd Bergmann" <arnd@arndb.de>
To: "Vignesh Raghavendra" <vigneshr@ti.com>, SoC <soc@kernel.org>,
arm <arm@kernel.org>
Cc: "SoC list" <soc@lists.linux.dev>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Tero Kristo" <kristo@kernel.org>,
"Nishanth Menon" <nm@ti.com>
Subject: Re: [GIT PULL 1/2] arm64: dts: ti: K3 updates for v7.1
Date: Fri, 03 Apr 2026 00:00:32 +0200 [thread overview]
Message-ID: <1ed625c0-e977-42d4-85f0-91e90a4c3547@app.fastmail.com> (raw)
In-Reply-To: <e724f95d-09d0-4ede-9ed4-0ce782d81058@ti.com>
On Wed, Apr 1, 2026, at 19:14, Vignesh Raghavendra wrote:
Hi Vignesh,
I've merged this now, but I see that there are a number of
patches that look like they should have been part of an
earlier pull request for 7.0 and possibly backports:
> Generic Fixes/Cleanups:
> - ti,min-output-impedance addition to all K3 board DT files
>
> AM69 Aquila:
> - Fix DP regulator enable GPIO
>
> AM62A7-SK:
> - Fix pin name in comment from M19 to N22
>
> AM62L3 EVM:
> - Disable MMC1 internal pulls on data pins
>
> AM62P:
> - SK: Disable MMC1 internal pulls on data pins and enable Main UART
Can you have a look to see if my intuition is right on these
ones, and make sure they get merged more quickly in the future?
Arnd
next prev parent reply other threads:[~2026-04-02 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 17:14 [GIT PULL 1/2] arm64: dts: ti: K3 updates for v7.1 Vignesh Raghavendra
2026-04-01 17:18 ` [GIT PULL 2/2] arm64: defconfig: TI " Vignesh Raghavendra
2026-04-02 22:00 ` Arnd Bergmann [this message]
2026-04-06 6:33 ` [GIT PULL 1/2] arm64: dts: ti: " Vignesh Raghavendra
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=1ed625c0-e977-42d4-85f0-91e90a4c3547@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=soc@kernel.org \
--cc=soc@lists.linux.dev \
--cc=vigneshr@ti.com \
/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