linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc3
Date: Fri, 22 Sep 2023 17:19:07 +0100	[thread overview]
Message-ID: <20230922161907.GB23332@willie-the-truck> (raw)

Hi Linus,

Please pull this small crop of relatively boring arm64 fixes for -rc3.

That's not to say we don't have any juicy bugs, however, it's just that
fixes for those are likely to come via -mm and -tip for a hugetlb and an
atomics issue respectively. I get left with the documentation...

Cheers,

Will

--->8

The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:

  Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 44a5b6b5c7fee5146572b4c57f0d9d9c398d1033:

  arm64: Document missing userspace visible fields in ID_AA64ISAR2_EL1 (2023-09-18 11:59:02 +0100)

----------------------------------------------------------------
arm64 fixes for -rc3

- Fix detection of "ClearBHB" and "Hinted Conditional Branch" features

- Fix broken wildcarding for Arm PMU MAINTAINERS entry

- Add missing documentation for userspace-visible ID register fields

----------------------------------------------------------------
Kristina Martsenko (1):
      arm64: cpufeature: Fix CLRBHB and BC detection

Mark Brown (3):
      arm64/sme: Include ID_AA64PFR1_EL1.SME in cpu-feature-registers.rst
      arm64/hbc: Document HWCAP2_HBC
      arm64: Document missing userspace visible fields in ID_AA64ISAR2_EL1

Oliver Upton (1):
      MAINTAINERS: Use wildcard pattern for ARM PMU headers

 Documentation/arch/arm64/cpu-feature-registers.rst | 12 ++++++++++++
 Documentation/arch/arm64/elf_hwcaps.rst            |  3 +++
 MAINTAINERS                                        |  2 +-
 arch/arm64/include/asm/cpufeature.h                |  2 +-
 arch/arm64/kernel/cpufeature.c                     |  3 ++-
 arch/arm64/tools/sysreg                            |  6 +++++-
 6 files changed, 24 insertions(+), 4 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-09-22 16:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 16:19 Will Deacon [this message]
2023-09-22 20:19 ` [GIT PULL] arm64 fixes for -rc3 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02 11:11 Will Deacon
2024-02-02 20:43 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22  0:07 ` Linus Torvalds
2020-02-22  0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31  4:25 ` pr-tracker-bot
2019-01-20  0:04 Will Deacon
2019-01-20  3:29 ` Linus Torvalds
2019-01-20  4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 Will Deacon

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=20230922161907.GB23332@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).