mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] soc: fixes for 6.13, part 3
Date: Fri, 23 May 2025 15:31:03 +0200	[thread overview]
Message-ID: <de1a7a9e-7823-4f98-bf9e-99d8722c28b8@app.fastmail.com> (raw)

The following changes since commit 15eaaa71e8ef142b122942b35653d513cfb90050:

  Merge tag 'imx-fixes-6.15-2' of https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into arm/fixes (2025-05-10 11:10:38 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/soc-fixes-6.15-3

for you to fetch changes up to 070d04f002ddc308b053df4723e83cf43719fda0:

  Merge tag 'mvebu-fixes-6.15-1' of https://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu into arm/fixes (2025-05-21 23:26:54 +0200)

----------------------------------------------------------------
soc: fixes for 6.13, part 3

A few last minute fixes:

 - two driver fixes for samsung/google platforms, both addressing
   mistakes in changes from the 6.15 merge window

 - a revert for an allwinner devicetree change that caused problems

 - a fix for an older regression with the LEDs on Marvell Armada 3720

 - a defconfig change to enable chacha20 again after a crypto
   subsystem change in 6.15 inadventently turned it off

----------------------------------------------------------------
Arnd Bergmann (3):
      Merge tag 'samsung-fixes-6.15' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into arm/fixes
      Merge tag 'sunxi-fixes-for-6.15' of https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into arm/fixes
      Merge tag 'mvebu-fixes-6.15-1' of https://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu into arm/fixes

Fabio Estevam (1):
      arm64: defconfig: Ensure CRYPTO_CHACHA20_NEON is selected

Gabor Juhos (1):
      arm64: dts: marvell: uDPU: define pinctrl state for alarm LEDs

Ivaylo Ivanov (1):
      soc: samsung: usi: prevent wrong bits inversion during unconfiguring

Jernej Skrabec (1):
      Revert "arm64: dts: allwinner: h6: Use RSB for AXP805 PMIC connection"

Tudor Ambarus (1):
      firmware: exynos-acpm: check saved RX before bailing out on empty RX queue

 .../boot/dts/allwinner/sun50i-h6-beelink-gs1.dts   | 38 +++++++++----------
 .../boot/dts/allwinner/sun50i-h6-orangepi-3.dts    | 14 +++----
 .../boot/dts/allwinner/sun50i-h6-orangepi.dtsi     | 22 +++++------
 arch/arm64/boot/dts/marvell/armada-3720-uDPU.dtsi  |  8 +++-
 arch/arm64/configs/defconfig                       |  2 +-
 drivers/firmware/samsung/exynos-acpm.c             | 44 +++++++++++++++-------
 drivers/soc/samsung/exynos-usi.c                   |  2 +-
 7 files changed, 75 insertions(+), 55 deletions(-)

             reply	other threads:[~2025-05-23 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 13:31 Arnd Bergmann [this message]
2025-05-23 15:21 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-01-11 14:41 Arnd Bergmann
2025-01-11 20:01 ` 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=de1a7a9e-7823-4f98-bf9e-99d8722c28b8@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®