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.19-rc3/rc4
Date: Fri, 17 Jun 2022 19:35:23 +0100 [thread overview]
Message-ID: <YqzJa4UPCNQg2pAR@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below (they can wait until -rc4 if
travelling). Thanks.
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -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 c50f11c6196f45c92ca48b16a5071615d4ae0572:
arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer (2022-06-17 19:06:06 +0100)
----------------------------------------------------------------
arm64 fixes for 5.19-rc3:
- Revert the moving of the jump labels initialisation before
setup_machine_fdt(). The bug was fixed in drivers/char/random.c.
- Ftrace fixes: branch range check and consistent handling of PLTs.
- Clean rather than invalidate FROM_DEVICE buffers at start of DMA
transfer (safer if such buffer is mapped in user space). A cache
invalidation is done already at the end of the transfer.
- A couple of clean-ups (unexport symbol, remove unused label).
----------------------------------------------------------------
Catalin Marinas (1):
Revert "arm64: Initialize jump labels before setup_machine_fdt()"
Mark Brown (1):
arm64/cpufeature: Unexport set_cpu_feature()
Mark Rutland (3):
arm64: ftrace: fix branch range checks
arm64: ftrace: consistently handle PLTs.
arm64: ftrace: remove redundant label
Will Deacon (1):
arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer
arch/arm64/kernel/cpufeature.c | 1 -
arch/arm64/kernel/entry-ftrace.S | 1 -
arch/arm64/kernel/ftrace.c | 137 +++++++++++++++++++--------------------
arch/arm64/kernel/setup.c | 7 +-
arch/arm64/mm/cache.S | 2 -
5 files changed, 69 insertions(+), 79 deletions(-)
--
Catalin
next reply other threads:[~2022-06-17 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 18:35 Catalin Marinas [this message]
2022-06-17 19:22 ` [GIT PULL] arm64 fixes for 5.19-rc3/rc4 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=YqzJa4UPCNQg2pAR@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