From: Vignesh Raghavendra <vigneshr@ti.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm-soc <arm@kernel.org>, SoC <soc@kernel.org>
Cc: Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Nishanth Menon <nm@ti.com>
Subject: [GIT PULL] arm64: dts: ti: K3 devicetree updates for v6.11 - part2
Date: Mon, 15 Jul 2024 23:37:42 +0530 [thread overview]
Message-ID: <aacd1e96-9ff4-4222-9f4d-29e63041f7fb@ti.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1287 bytes --]
Hi ARM SoC Maintainers,
Please pull below PR which consists of a late fix to my earlier pull request:
https://lore.kernel.org/linux-arm-kernel/37f251a1-f3bd-402f-ab22-cf786c3871d7@ti.com/
The following changes since commit 6406c5d5512c0814b8c155df7f833a98d9069a72:
arm64: dts: ti: k3-am62a7-sk: Reserve 576MiB of global CMA (2024-07-03 19:51:21 +0530)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-k3-dt-for-v6.11-part2
for you to fetch changes up to cc5049007d722364bca4a4eeb619d5629733a004:
arm64: dts: ti: k3-j784s4-evm: Consolidate serdes0 references (2024-07-12 17:08:40 +0530)
----------------------------------------------------------------
Late fixes towards v6.11-rc1
First patch fixes warning splat seen on J784S4 due to overlapping
serdes0 lane. Second patch cleans up the serdes0 references for readability
----------------------------------------------------------------
Andrew Halaney (2):
arm64: dts: ti: k3-j784s4-evm: Assign only lanes 0 and 1 to PCIe1
arm64: dts: ti: k3-j784s4-evm: Consolidate serdes0 references
arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 25 +++-------
1 file changed, 8 insertions(+), 17 deletions(-)
--
Regards
Vignesh
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
reply other threads:[~2024-07-15 19:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aacd1e96-9ff4-4222-9f4d-29e63041f7fb@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=olof@lixom.net \
--cc=soc@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
all inboxes | Powered by JetHome®