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 -rc1
Date: Thu, 4 May 2023 15:22:48 +0100	[thread overview]
Message-ID: <20230504142247.GA18895@willie-the-truck> (raw)

Hi Linus,

Please pull these few arm64 fixes that came in during the merge window for
-rc1. The main thing is restoring the pointer authentication hwcaps, which
disappeared during some recent refactoring.

Thanks,

Will

--->8

The following changes since commit eeb3557cc188e42ae7f7bef2d6dc5bf0e078412e:

  Merge branch 'for-next/sysreg' into for-next/core (2023-04-20 18:03:07 +0100)

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 0fddb79bf283a561eb81f09d01f5ac8f61bf8966:

  arm64: lds: move .got section out of .text (2023-05-02 13:12:45 +0100)

----------------------------------------------------------------
arm64 fixes for -rc1

- Fix regression in CPU erratum workaround when disabling the MMU

- Fix detection of pointer authentication hwcaps

- Avoid writeable, executable ELF sections in vmlinux

----------------------------------------------------------------
Fangrui Song (1):
      arm64: lds: move .got section out of .text

Kristina Martsenko (1):
      arm64: cpufeature: Fix pointer auth hwcaps

Neeraj Upadhyay (1):
      arm64: Fix label placement in record_mmu_state()

ndesaulniers@google.com (1):
      arm64: kernel: remove SHF_WRITE|SHF_EXECINSTR from .idmap.text

 arch/arm64/kernel/cpu-reset.S   |  2 +-
 arch/arm64/kernel/cpufeature.c  | 12 ++++++------
 arch/arm64/kernel/head.S        |  4 ++--
 arch/arm64/kernel/sleep.S       |  2 +-
 arch/arm64/kernel/vmlinux.lds.S | 19 +++++++++----------
 arch/arm64/mm/proc.S            |  6 +++---
 6 files changed, 22 insertions(+), 23 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-05-04 14:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 14:22 Will Deacon [this message]
2023-05-04 19:49 ` [GIT PULL] arm64 fixes for -rc1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-01-19 16:05 Will Deacon
2024-01-19 16:34 ` Rob Herring
2024-01-19 16:58   ` Rob Herring
2024-01-19 22:50 ` pr-tracker-bot
2023-09-08 15:30 Will Deacon
2023-09-08 20:00 ` pr-tracker-bot
2022-12-16 15:51 Will Deacon
2022-12-16 19:50 ` pr-tracker-bot
2021-11-10 18:52 Will Deacon
2021-11-10 20:09 ` pr-tracker-bot
2021-02-26 11:09 [GIT PULL] arm64: Fixes " Will Deacon
2021-02-26 18:31 ` pr-tracker-bot
2019-09-20 13:37 Will Deacon
2019-09-20 19:10 ` pr-tracker-bot
2019-01-04 18:24 [GIT PULL] arm64: fixes " Will Deacon
2019-01-05 20:20 ` pr-tracker-bot
2017-03-01  4:51 [GIT PULL] arm64 " Will Deacon
2016-08-05 15:48 [GIT PULL] arm64: " Will Deacon
2014-12-16 17:50 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=20230504142247.GA18895@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).