From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] soc: fixes for 6.17, part 1
Date: Fri, 08 Aug 2025 22:53:37 +0200 [thread overview]
Message-ID: <828e73a2-23ae-442a-8d29-415a87b8ec4a@app.fastmail.com> (raw)
The following changes since commit 038d61fd642278bab63ee8ef722c50d10ab01e8f:
Linux 6.16 (2025-07-27 14:26:38 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/soc-fixes-6.17-1
for you to fetch changes up to 0c952efa0d7cf5258879406077df33d23cb06d5e:
Merge tag 'tegra-for-6.17-arm64-dt-v3' of https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into arm/fixes (2025-08-08 22:50:44 +0200)
----------------------------------------------------------------
soc: fixes for 6.17, part 1
These are a few patches to fix up bits that went missing during the
merge window: The tegra and s3c patches address trivial regressions
from conflicts, the bcm7445 makes the dt conform to the binding that
was made stricter.
----------------------------------------------------------------
Arnd Bergmann (2):
Merge tag 'arm-soc/for-6.16/devicetree-fixes' of https://github.com/Broadcom/stblinux into for-next
Merge tag 'tegra-for-6.17-arm64-dt-v3' of https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into arm/fixes
Bartosz Golaszewski (1):
ARM: s3c/gpio: complete the conversion to new GPIO value setters
Florian Fainelli (1):
ARM: dts: broadcom: Fix bcm7445 memory controller compatible
Thierry Reding (1):
arm64: tegra: Remove numa-node-id properties
arch/arm/boot/dts/broadcom/bcm7445.dtsi | 9 ++++++---
arch/arm/mach-s3c/gpio-samsung.c | 2 +-
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 3 ---
3 files changed, 7 insertions(+), 7 deletions(-)
next reply other threads:[~2025-08-08 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 20:53 Arnd Bergmann [this message]
2025-08-09 5:19 ` 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=828e73a2-23ae-442a-8d29-415a87b8ec4a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@lists.linux.dev \
--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®