public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Catalin Marinas <cmarinas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 6.19-rc6
Date: Sat, 17 Jan 2026 14:05:37 +0000	[thread overview]
Message-ID: <aWuXMab4BxnbUbOG@arm.com> (raw)

Hi Linus,

Please pull the arm64 fixes below. Thanks.

The following changes since commit bdf3f4176092df5281877cacf42f843063b4784d:

  arm64: Fix cleared E0POE bit after cpu_suspend()/resume() (2026-01-09 10:41:45 +0000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes

for you to fetch changes up to b9f5c38e4af1a094384650d2fc79fb992d6d5e64:

  arm_mpam: Use non-atomic bitops when modifying feature bitmap (2026-01-16 12:04:20 +0000)

----------------------------------------------------------------
arm64/mpam fix to use non-atomic bitops on struct mmap_props member
(atomicity not required). For kunit testing, the structure is packed to
avoid memcmp() errors but this affects atomic bitops as they have strict
alignment requirements.

Also remove a duplicate include in the mpam driver.

----------------------------------------------------------------
Ben Horgan (1):
      arm_mpam: Use non-atomic bitops when modifying feature bitmap

Jiapeng Chong (1):
      arm_mpam: Remove duplicate linux/srcu.h header

 drivers/resctrl/mpam_internal.h | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

-- 
Catalin


             reply	other threads:[~2026-01-17 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-17 14:05 Catalin Marinas [this message]
2026-01-19 13:53 ` [GIT PULL] arm64 fixes for 6.19-rc6 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=aWuXMab4BxnbUbOG@arm.com \
    --to=cmarinas@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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