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 -rc3
Date: Fri, 7 Jun 2024 12:30:18 +0100 [thread overview]
Message-ID: <20240607113018.GA24475@willie-the-truck> (raw)
Hi Linus,
Please pull these couple of minor fixes for -rc3. The summary's in the
tag, but neither are hugely interesting.
The main bug we have at the moment is an out-of-bounds access in the
contiguous pte code; Andrew should send you the fix via -mm shortly.
Cheers,
Will
--->8
The following changes since commit c3f38fa61af77b49866b006939479069cd451173:
Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)
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 5c40e428aea644c9d924e491b1bc22fa9f272bcc:
arm64/io: add constant-argument check (2024-06-05 13:30:58 +0100)
----------------------------------------------------------------
arm64 fix for -rc3
- Fix spurious CPU hotplug warning message from SETEND emulation code
- Fix the build when GCC wasn't inlining our I/O accessor internals
----------------------------------------------------------------
Arnd Bergmann (1):
arm64/io: add constant-argument check
Wei Li (1):
arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process
arch/arm64/include/asm/io.h | 36 ++++++++++++++++--------------------
arch/arm64/kernel/armv8_deprecated.c | 3 +++
2 files changed, 19 insertions(+), 20 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-06-07 11:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 11:30 Will Deacon [this message]
2024-06-07 22:07 ` [GIT PULL] arm64 fixes for -rc3 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-06 22:49 Will Deacon
2026-03-07 4:34 ` pr-tracker-bot
2025-06-20 10:50 Will Deacon
2025-06-20 17:29 ` pr-tracker-bot
2025-02-14 14:04 Will Deacon
2025-02-14 19:29 ` pr-tracker-bot
2024-02-02 11:11 Will Deacon
2024-02-02 20:43 ` pr-tracker-bot
2023-09-22 16:19 Will Deacon
2023-09-22 20:19 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22 0:07 ` Linus Torvalds
2020-02-22 0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31 4:25 ` pr-tracker-bot
2019-01-20 0:04 Will Deacon
2019-01-20 3:29 ` Linus Torvalds
2019-01-20 4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 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=20240607113018.GA24475@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