Linux-ARM-Kernel Archive on lore.kernel.org
 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: Wed, 10 Nov 2021 18:52:13 +0000	[thread overview]
Message-ID: <20211110185212.GA4786@willie-the-truck> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc1 to address issues spotted during the
merge window. There's the usual summary in the tag and we have at least one
more fix already pending for next week.

Cheers,

Will

--->8

The following changes since commit e6359798f62da66a4a48061d2324a69ea59ff39b:

  Merge branch 'for-next/fixes' into for-next/core (2021-10-29 12:27:53 +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 c7c386fbc20262c1d911c615c65db6a58667d92c:

  arm64: pgtable: make __pte_to_phys/__phys_to_pte_val inline functions (2021-11-08 10:05:54 +0000)

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

- Fix double-evaluation of 'pte' macro argument when using 52-bit PAs

- Fix signedness of some MTE prctl PR_* constants

- Fix kmemleak memory usage by skipping early pgtable allocations

- Fix printing of CPU feature register strings

- Remove redundant -nostdlib linker flag for vDSO binaries

----------------------------------------------------------------
Arnd Bergmann (1):
      arm64: pgtable: make __pte_to_phys/__phys_to_pte_val inline functions

Masahiro Yamada (1):
      arm64: vdso: remove -nostdlib compiler flag

Peter Collingbourne (1):
      arm64: mte: change PR_MTE_TCF_NONE back into an unsigned long

Qian Cai (1):
      arm64: Track no early_pgtable_alloc() for kmemleak

Reiji Watanabe (1):
      arm64: arm64_ftr_reg->name may not be a human-readable string

 arch/arm/mm/kasan_init.c          |  2 +-
 arch/arm64/include/asm/pgtable.h  | 12 +++++++++---
 arch/arm64/kernel/cpufeature.c    | 10 +++++++---
 arch/arm64/kernel/vdso/Makefile   |  2 +-
 arch/arm64/kernel/vdso32/Makefile |  2 +-
 arch/arm64/mm/kasan_init.c        |  5 +++--
 arch/arm64/mm/mmu.c               |  3 ++-
 include/linux/memblock.h          |  2 +-
 include/uapi/linux/prctl.h        |  2 +-
 mm/memblock.c                     |  9 ++++++---
 tools/include/uapi/linux/prctl.h  |  2 +-
 11 files changed, 33 insertions(+), 18 deletions(-)

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

             reply	other threads:[~2021-11-10 18:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 18:52 Will Deacon [this message]
2021-11-10 20:09 ` [GIT PULL] arm64 fixes for -rc1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-06-26 10:59 Will Deacon
2026-06-26 15:45 ` pr-tracker-bot
2026-02-20 15:41 Will Deacon
2026-02-20 20:50 ` pr-tracker-bot
2025-10-07  8:28 Will Deacon
2025-10-07 16:13 ` pr-tracker-bot
2025-06-05 13:41 Will Deacon
2025-06-05 18:53 ` pr-tracker-bot
2024-07-26  8:42 Will Deacon
2024-07-26 18:07 ` pr-tracker-bot
2024-05-23 10:20 Will Deacon
2024-05-23 19:28 ` pr-tracker-bot
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
2023-05-04 14:22 Will Deacon
2023-05-04 19:49 ` pr-tracker-bot
2022-12-16 15:51 Will Deacon
2022-12-16 19:50 ` 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=20211110185212.GA4786@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