linux-arm-kernel.lists.infradead.org archive mirror
 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-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for 5.7-rc1
Date: Thu, 9 Apr 2020 17:50:51 +0100	[thread overview]
Message-ID: <20200409165049.GA872@gaia> (raw)

Hi Linus,

Please pull the arm64 fixes below (on top of the previous pull request
for 5.7-rc1). Thanks.

The following changes since commit b2a84de2a2deb76a6a51609845341f508c518c03:

  mm/mremap: Add comment explaining the untagging behaviour of mremap() (2020-03-26 11:28:57 +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 fc2266011accd5aeb8ebc335c381991f20e26e33:

  arm64: armv8_deprecated: Fix undef_hook mask for thumb setend (2020-04-08 18:19:20 +0100)

----------------------------------------------------------------
arm64 fixes:

- Ensure that the compiler and linker versions are aligned so that ld
  doesn't complain about not understanding a .note.gnu.property section
  (emitted when pointer authentication is enabled).

- Force -mbranch-protection=none when the feature is not enabled, in
  case a compiler may choose a different default value.

- Remove CONFIG_DEBUG_ALIGN_RODATA. It was never in defconfig and rarely
  enabled.

- Fix checking 16-bit Thumb-2 instructions checking mask in the
  emulation of the SETEND instruction (it could match the bottom half of
  a 32-bit Thumb-2 instruction).

----------------------------------------------------------------
Amit Daniel Kachhap (2):
      init/kconfig: Add LD_VERSION Kconfig
      arm64: Kconfig: ptrauth: Add binutils version check to fix mismatch

Ard Biesheuvel (1):
      arm64: remove CONFIG_DEBUG_ALIGN_RODATA feature

Fredrik Strupe (1):
      arm64: armv8_deprecated: Fix undef_hook mask for thumb setend

Mark Brown (1):
      arm64: Always force a branch protection mode when the compiler has one

 arch/arm64/Kconfig                        |  5 ++++-
 arch/arm64/Kconfig.debug                  | 13 -------------
 arch/arm64/Makefile                       |  7 ++++++-
 arch/arm64/include/asm/memory.h           | 12 +-----------
 arch/arm64/kernel/armv8_deprecated.c      |  2 +-
 drivers/firmware/efi/libstub/arm64-stub.c |  8 +++-----
 init/Kconfig                              |  4 ++++
 7 files changed, 19 insertions(+), 32 deletions(-)

-- 
Catalin

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

             reply	other threads:[~2020-04-09 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 16:50 Catalin Marinas [this message]
2020-04-09 18:10 ` [GIT PULL] arm64 fixes for 5.7-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=20200409165049.GA872@gaia \
    --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;
as well as URLs for NNTP newsgroup(s).