From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: torvalds@linux-foundation.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MIPS changes pt2 for v6.13
Date: Fri, 29 Nov 2024 09:33:58 +0100 [thread overview]
Message-ID: <Z0l8dqSzSPrsbmFj@alpha.franken.de> (raw)
The following changes since commit 56131e6d1fcce8e7359a2445711cc1a4ddb8325c:
mips: dts: realtek: Add I2C controllers (2024-11-12 15:51:21 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_6.13_1
for you to fetch changes up to 4fbd66d8254cedfd1218393f39d83b6c07a01917:
MIPS: Loongson64: DTS: Really fix PCIe port nodes for ls7a (2024-11-23 11:53:21 +0100)
----------------------------------------------------------------
- fix for loongson64 device tree
- add SPI nand to realtek device tree
- change clock tree for mobileye
----------------------------------------------------------------
Chris Packham (1):
mips: dts: realtek: Add SPI NAND controller
Théo Lebrun (2):
MIPS: mobileye: eyeq5: use OLB as provider for fixed factor clocks
MIPS: mobileye: eyeq6h: add OLB nodes OLB and remove fixed clocks
Xi Ruoyao (1):
MIPS: Loongson64: DTS: Really fix PCIe port nodes for ls7a
arch/mips/boot/dts/loongson/ls7a-pch.dtsi | 73 +++++-
arch/mips/boot/dts/mobileye/eyeq5-clocks.dtsi | 270 ---------------------
arch/mips/boot/dts/mobileye/eyeq5.dtsi | 30 ++-
.../boot/dts/mobileye/eyeq6h-fixed-clocks.dtsi | 52 ----
arch/mips/boot/dts/mobileye/eyeq6h.dtsi | 73 +++++-
arch/mips/boot/dts/realtek/rtl930x.dtsi | 13 +
6 files changed, 166 insertions(+), 345 deletions(-)
delete mode 100644 arch/mips/boot/dts/mobileye/eyeq5-clocks.dtsi
delete mode 100644 arch/mips/boot/dts/mobileye/eyeq6h-fixed-clocks.dtsi
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2024-11-29 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 8:33 Thomas Bogendoerfer [this message]
2024-11-29 18:55 ` pr-tracker-bot
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=Z0l8dqSzSPrsbmFj@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=torvalds@linux-foundation.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®