The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
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.9-rc1
Date: Fri, 22 Mar 2024 00:09:14 +0000	[thread overview]
Message-ID: <ZfzMKqtxAfHwHY3p@arm.com> (raw)

Hi Linus,

Please pull the arm64 update and perf fix below. Thanks.

The following changes since commit 1ef21fcd6a50f011680dbbd678c1bea8e3f67ab9:

  Revert "mm: add arch hook to validate mmap() prot flags" (2024-03-13 10:59:38 +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 1d63d1d9e5c5cb2e7c7ca75751a5eaf67c5623a7:

  perf: starfive: fix 64-bit only COMPILE_TEST condition (2024-03-19 19:01:39 +0000)

----------------------------------------------------------------
arm64 fix/update:

- Re-instate the CPUMASK_OFFSTACK option for arm64 when NR_CPUS > 256.
  The bug that led to the initial revert was the cpufreq-dt code not
  using zalloc_cpumask_var().

- Make the STARFIVE_STARLINK_PMU config option depend on 64BIT to
  prevent compile-test failures on 32-bit architectures due to missing
  writeq().

----------------------------------------------------------------
Christoph Lameter (Ampere) (1):
      ARM64: Dynamically allocate cpumasks and increase supported CPUs to 512

Conor Dooley (1):
      perf: starfive: fix 64-bit only COMPILE_TEST condition

 arch/arm64/Kconfig   | 3 ++-
 drivers/perf/Kconfig | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

-- 
Catalin

             reply	other threads:[~2024-03-22  0:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22  0:09 Catalin Marinas [this message]
2024-03-22  0:32 ` [GIT PULL] arm64 fixes for 6.9-rc1 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=ZfzMKqtxAfHwHY3p@arm.com \
    --to=catalin.marinas@arm.com \
    --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