From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 4.18-rc2
Date: Fri, 22 Jun 2018 18:37:17 +0100 [thread overview]
Message-ID: <20180622173714.jtvicri5szn4dzb4@armageddon.cambridge.arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
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 71c8fc0c96abf8e53e74ed4d891d671e585f9076:
arm64: mm: Ensure writes to swapper are ordered wrt subsequent cache maintenance (2018-06-22 17:23:40 +0100)
----------------------------------------------------------------
arm64 fixes:
- Zero buffers allocated with FORCE_CONTIGUOUS explicitly until the CMA
code honours __GFP_ZERO
- notrace annotation for secondary_start_kernel()
- Use early_param() instead of __setup() for "kpti=" as it is needed for
the cpufeature callback remapping swapper to non-global mappings
- Ensure writes to swapper are ordered wrt subsequent cache maintenance
in the kpti non-global remapping code
----------------------------------------------------------------
Marek Szyprowski (1):
arm64: dma-mapping: clear buffers allocated with FORCE_CONTIGUOUS flag
Will Deacon (2):
arm64: kpti: Use early_param for kpti= command-line option
arm64: mm: Ensure writes to swapper are ordered wrt subsequent cache maintenance
Zhizhou Zhang (1):
arm64: make secondary_start_kernel() notrace
arch/arm64/kernel/cpufeature.c | 2 +-
arch/arm64/kernel/smp.c | 2 +-
arch/arm64/mm/dma-mapping.c | 9 +++++----
arch/arm64/mm/proc.S | 5 +++--
4 files changed, 10 insertions(+), 8 deletions(-)
--
Catalin
reply other threads:[~2018-06-22 17:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180622173714.jtvicri5szn4dzb4@armageddon.cambridge.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.deacon@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).