Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 8 Jun 2023 21:51:44 +0100
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 -rc6
Message-ID: <20230608205144.GA2470@willie-the-truck>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

Hi Linus,

Please pull these two tiny arm64 fixes for -rc6. One fixes a build
breakage when MAX_ORDER can be nonsensical if CONFIG_EXPERT=y and the
other fixes the address masking for perf's page fault software events
so that it is consistent amongst them.

Cheers,

Will

--->8

The following changes since commit c4c597f1b367433c52c531dccd6859a39b4580fb:

  arm64: mte: Do not set PG_mte_tagged if tags were not initialized (2023-05-16 14:59:16 +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 0e2aba694866b451db0932a6706683c48379134c:

  arm64: mm: pass original fault address to handle_mm_fault() in PER_VMA_LOCK block (2023-06-02 13:02:44 +0100)

----------------------------------------------------------------
arm64 fixes for -rc6

- Fix build breakage due to bogus MAX_ORDER definitions on !4k pages

- Avoid masking fault address for perf software events

----------------------------------------------------------------
Catalin Marinas (1):
      arm64: Remove the ARCH_FORCE_MAX_ORDER config input prompt

Jisheng Zhang (1):
      arm64: mm: pass original fault address to handle_mm_fault() in PER_VMA_LOCK block

 arch/arm64/Kconfig    | 2 +-
 arch/arm64/mm/fault.c | 3 +--
 2 files changed, 2 insertions(+), 3 deletions(-)