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.17-rc1
Date: Fri, 21 Jan 2022 16:59:49 +0000 [thread overview]
Message-ID: <YermhR/kQO+dg7P/@arm.com> (raw)
Hi Linus,
Please pull the arm64 updates below, some fixes that turned up during
the merging window. Thanks.
The following changes since commit 945409a6ef442cfe5f2f14e5626d4306d53100f0:
Merge branches 'for-next/misc', 'for-next/cache-ops-dzp', 'for-next/stacktrace', 'for-next/xor-neon', 'for-next/kasan', 'for-next/armv8_7-fp', 'for-next/atomics', 'for-next/bti', 'for-next/sve', 'for-next/kselftest' and 'for-next/kcsan', remote-tracking branch 'arm64/for-next/perf' into for-next/core (2022-01-05 18:14:32 +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 bb425a7598479fa0f171ec806033c440f218b0ce:
arm64: mm: apply __ro_after_init to memory_limit (2022-01-20 09:15:16 +0000)
----------------------------------------------------------------
arm64 fixes/cleanups:
- Add brackets to the io_stop_wc macro.
- Avoid -Warray-bounds warning with the LSE atomics inline asm.
- Apply __ro_after_init to memory_limit.
----------------------------------------------------------------
Kees Cook (1):
arm64: atomics: lse: Dereference matching size
Peng Fan (1):
arm64: mm: apply __ro_after_init to memory_limit
Xiongfeng Wang (1):
asm-generic: Add missing brackets for io_stop_wc macro
arch/arm64/include/asm/atomic_lse.h | 2 +-
arch/arm64/include/asm/cmpxchg.h | 2 +-
arch/arm64/mm/init.c | 2 +-
include/asm-generic/barrier.h | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
--
Catalin
next reply other threads:[~2022-01-21 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 16:59 Catalin Marinas [this message]
2022-01-22 8:06 ` 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=YermhR/kQO+dg7P/@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: 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
all inboxes | Powered by JetHome®