From: Palmer Dabbelt <palmerdabbelt@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: [GIT PULL] RISC-V Patches for the 5.6 Merge Window, Part 1
Date: Fri, 31 Jan 2020 03:00:32 -0800 (PST) [thread overview]
Message-ID: <mhng-84383e2c-cd04-4915-a165-f10367359beb@palmerdabbelt-glaptop1> (raw)
The following changes since commit def9d2780727cec3313ed3522d0123158d87224d:
Linux 5.5-rc7 (2020-01-19 16:02:49 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.6-mw0
for you to fetch changes up to 61ffb9d27860769c5d5596f6e4cca3cded2755e0:
riscv: dts: Add DT support for SiFive FU540 GPIO driver (2020-01-29 14:58:08 +0000)
----------------------------------------------------------------
RISC-V Patches for the 5.6 Merge Window, Part 1
This tag contains a handful of patches that I'd like to target for this merge
window:
* Support for kasan.
* 32-bit physical addresses on rv32i-based systems.
* Support for CONFIG_DEBUG_VIRTUAL
* DT entry for the FU540 GPIO controller, which has recently had a device
driver merged.
These boot a buildroot-based system on QEMU's virt board for me.
----------------------------------------------------------------
Nick Hu (3):
kasan: No KASAN's memmove check if archs don't have it.
riscv: Add KASAN support
kasan: Add riscv to KASAN documentation.
Olof Johansson (1):
riscv: keep 32-bit kernel to 32-bit phys_addr_t
Yash Shah (1):
riscv: dts: Add DT support for SiFive FU540 GPIO driver
Zong Li (1):
riscv: mm: add support for CONFIG_DEBUG_VIRTUAL
Documentation/dev-tools/kasan.rst | 4 +-
arch/riscv/Kconfig | 4 +-
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 15 ++-
.../riscv/boot/dts/sifive/hifive-unleashed-a00.dts | 4 +
arch/riscv/include/asm/kasan.h | 27 ++++++
arch/riscv/include/asm/page.h | 16 +++-
arch/riscv/include/asm/pgtable-64.h | 5 +
arch/riscv/include/asm/string.h | 9 ++
arch/riscv/kernel/head.S | 3 +
arch/riscv/kernel/riscv_ksyms.c | 2 +
arch/riscv/kernel/setup.c | 5 +
arch/riscv/kernel/vmlinux.lds.S | 1 +
arch/riscv/lib/memcpy.S | 5 +-
arch/riscv/lib/memset.S | 5 +-
arch/riscv/mm/Makefile | 8 ++
arch/riscv/mm/kasan_init.c | 104 +++++++++++++++++++++
arch/riscv/mm/physaddr.c | 37 ++++++++
mm/kasan/common.c | 2 +
18 files changed, 245 insertions(+), 11 deletions(-)
create mode 100644 arch/riscv/include/asm/kasan.h
create mode 100644 arch/riscv/mm/kasan_init.c
create mode 100644 arch/riscv/mm/physaddr.c
reply other threads:[~2020-01-31 11:00 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=mhng-84383e2c-cd04-4915-a165-f10367359beb@palmerdabbelt-glaptop1 \
--to=palmerdabbelt@google.com \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
--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;
as well as URLs for NNTP newsgroup(s).