mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, 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: Mon, 6 Apr 2026 12:03:28 +0530	[thread overview]
Message-ID: <f70d16ec-f472-4b96-94d0-43eb4acffff8@ti.com> (raw)
In-Reply-To: <1ed625c0-e977-42d4-85f0-91e90a4c3547@app.fastmail.com>

Hi Arnd,

On 03/04/26 03:30, Arnd Bergmann wrote:
> 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?
> 

Ah yes. These are non urgent fixes in terms of impact on functionality
(except AM69 Aquila one perhaps), so decided to club them into the v7.1.
But, will keep in mind to send them earlier next time. Thanks!



-- 
Regards
Vignesh
https://ti.com/opensource


      reply	other threads:[~2026-04-06  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 17:14 Vignesh Raghavendra
2026-04-01 17:18 ` [GIT PULL 2/2] arm64: defconfig: TI " Vignesh Raghavendra
2026-04-02 22:00 ` [GIT PULL 1/2] arm64: dts: ti: " Arnd Bergmann
2026-04-06  6:33   ` Vignesh Raghavendra [this message]

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=f70d16ec-f472-4b96-94d0-43eb4acffff8@ti.com \
    --to=vigneshr@ti.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --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 \
    /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

all inboxes | Powered by JetHome®