linux-kernel.vger.kernel.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 -rc4
Date: Fri, 22 Apr 2022 12:20:29 +0100	[thread overview]
Message-ID: <20220422112028.GA9901@willie-the-truck> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc4. There's no real pattern to them, but
the main one fixes our pmd_leaf() definition to resolve a NULL dereference
on the migration path.

Cheers,

Will

--->8

The following changes since commit d02b4dd84e1a90f7f1444d027c0289bf355b0d5a:

  perf/imx_ddr: Fix undefined behavior due to shift overflowing the constant (2022-04-08 14:17:57 +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 23bc8f69f0eceecbb87c3801d2e48827d2dca92b:

  arm64: mm: fix p?d_leaf() (2022-04-22 11:28:36 +0100)

----------------------------------------------------------------
arm64 fixes for -rc4

- Fix PMU event validation in the absence of any event counters

- Fix allmodconfig build using clang in conjunction with binutils

- Fix definitions of pXd_leaf() to handle PROT_NONE entries

- More typo fixes

----------------------------------------------------------------
Ken Kurematsu (1):
      arm64: fix typos in comments

Muchun Song (1):
      arm64: mm: fix p?d_leaf()

Nathan Chancellor (1):
      arm64: Improve HAVE_DYNAMIC_FTRACE_WITH_REGS selection for clang

Rob Herring (1):
      arm_pmu: Validate single/group leader events

 arch/arm64/Kconfig               | 15 ++++++++++++---
 arch/arm64/include/asm/pgtable.h |  4 ++--
 drivers/perf/arm_pmu.c           | 10 ++++------
 3 files changed, 18 insertions(+), 11 deletions(-)

             reply	other threads:[~2022-04-22 11:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 11:20 Will Deacon [this message]
2022-04-22 21:19 ` [GIT PULL] arm64 fixes for -rc4 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-01-13 10:29 Will Deacon
2023-01-13 13:58 ` pr-tracker-bot
2022-09-02 11:12 Will Deacon
2022-09-02 18:30 ` pr-tracker-bot
2021-12-03 13:19 Will Deacon
2021-12-03 18:53 ` pr-tracker-bot
2020-11-13 12:39 GIT " Will Deacon
2020-11-13 12:44 ` [GIT " Will Deacon
2020-11-13 17:25   ` Linus Torvalds
2020-07-04 13:05 Will Deacon
2020-07-05 17:35 ` pr-tracker-bot
2019-10-17 23:43 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-18  0:06 ` Linus Torvalds
2019-10-18 17:41   ` Will Deacon
2019-10-18 19:17     ` Linus Torvalds
2019-10-21  6:46       ` Ingo Molnar
2019-10-21 11:45         ` Linus Torvalds
2019-10-22  8:16         ` Uwe Kleine-König
2019-10-18  0:15 ` pr-tracker-bot
2019-10-18 20:09 ` Jayachandran Chandrasekharan Nair
2019-06-07 15:13 [GIT PULL] arm64: fixes " Will Deacon
2019-06-07 16:45 ` pr-tracker-bot
2019-04-05 17:17 [GIT PULL] arm64 " Catalin Marinas
2019-04-05 23:50 ` pr-tracker-bot
2018-09-14 16:19 [GIT PULL] arm64: " Will Deacon
2017-12-15 18:31 Will Deacon
2017-08-04 18:32 Will Deacon
2016-06-17 17:07 Will Deacon
2015-05-14 15:48 Will Deacon
2015-01-09 15:22 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=20220422112028.GA9901@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).