From: Catalin Marinas <catalin.marinas@arm.com> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [GIT PULL] arm64 fixes for 5.13-rc4 Date: Thu, 27 May 2021 20:02:32 +0100 [thread overview] Message-ID: <20210527190230.GA4576@arm.com> (raw) Hi Linus, Please pull the arm64 fixes below. Thanks. The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc: Linux 5.13-rc2 (2021-05-16 15:27:44 -0700) 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 e69012400b0cb42b2070748322cb72f9effec00f: arm64: mm: don't use CON and BLK mapping if KFENCE is enabled (2021-05-25 14:04:38 +0100) ---------------------------------------------------------------- arm64 fixes: - Don't use contiguous or block mappings for the linear map when KFENCE is enabled. - Fix link in the arch_counter_enforce_ordering() comment. ---------------------------------------------------------------- Catalin Marinas (1): arm64: Fix stale link in the arch_counter_enforce_ordering() comment Jisheng Zhang (1): arm64: mm: don't use CON and BLK mapping if KFENCE is enabled arch/arm64/include/asm/barrier.h | 2 +- arch/arm64/mm/mmu.c | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) -- Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [GIT PULL] arm64 fixes for 5.13-rc4 Date: Thu, 27 May 2021 20:02:32 +0100 [thread overview] Message-ID: <20210527190230.GA4576@arm.com> (raw) Hi Linus, Please pull the arm64 fixes below. Thanks. The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc: Linux 5.13-rc2 (2021-05-16 15:27:44 -0700) 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 e69012400b0cb42b2070748322cb72f9effec00f: arm64: mm: don't use CON and BLK mapping if KFENCE is enabled (2021-05-25 14:04:38 +0100) ---------------------------------------------------------------- arm64 fixes: - Don't use contiguous or block mappings for the linear map when KFENCE is enabled. - Fix link in the arch_counter_enforce_ordering() comment. ---------------------------------------------------------------- Catalin Marinas (1): arm64: Fix stale link in the arch_counter_enforce_ordering() comment Jisheng Zhang (1): arm64: mm: don't use CON and BLK mapping if KFENCE is enabled arch/arm64/include/asm/barrier.h | 2 +- arch/arm64/mm/mmu.c | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-05-27 19:02 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 19:02 Catalin Marinas [this message] 2021-05-27 19:02 ` [GIT PULL] arm64 fixes for 5.13-rc4 Catalin Marinas 2021-05-27 22:04 ` pr-tracker-bot 2021-05-27 22:04 ` 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=20210527190230.GA4576@arm.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.