From: Paul Walmsley <paul.walmsley@sifive.com>
To: torvalds@linux-foundation.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V updates for v5.5-rc4
Date: Sun, 29 Dec 2019 09:22:29 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1912290921260.204131@viisi.sifive.com> (raw)
Linus,
The following changes since commit 46cf053efec6a3a5f343fead837777efe8252a46:
Linux 5.5-rc3 (2019-12-22 17:02:23 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.5-rc4
for you to fetch changes up to 1833e327a5ea1d1f356fbf6ded0760c9ff4b0594:
riscv: export flush_icache_all to modules (2019-12-27 21:51:01 -0800)
----------------------------------------------------------------
RISC-V updates for v5.5-rc4
One important fix for RISC-V:
- Redirect any incoming syscall with an ID less than -1 to
sys_ni_syscall, rather than allowing them to fall through into the
syscall handler.
and two minor build fixes:
- Export __asm_copy_{from,to}_user() from where they are defined.
This fixes a build error triggered by some randconfigs.
- Export flush_icache_all(). I'd resisted this before, since
historically we didn't want modules to be able to flush the I$
directly; but apparently everyone else is doing it now.
----------------------------------------------------------------
David Abdurachmanov (1):
riscv: reject invalid syscalls below -1
Luc Van Oostenryck (1):
riscv: fix compile failure with EXPORT_SYMBOL() & !MMU
Olof Johansson (1):
riscv: export flush_icache_all to modules
arch/riscv/kernel/entry.S | 1 +
arch/riscv/kernel/riscv_ksyms.c | 3 ---
arch/riscv/lib/uaccess.S | 4 ++++
arch/riscv/mm/cacheflush.c | 1 +
4 files changed, 6 insertions(+), 3 deletions(-)
Kernel object size difference:
text data bss dec hex filename
6896332 2329908 313920 9540160 919240 vmlinux.rv64.orig
6896379 2329908 313920 9540207 91926f vmlinux.rv64.patched
6656967 1939072 257576 8853615 87186f vmlinux.rv32.orig
6656994 1939072 257576 8853642 87188a vmlinux.rv32.patched
1171666 353368 130024 1655058 194112 vmlinux.nommu_virt.orig
1171674 353368 130024 1655066 19411a vmlinux.nommu_virt.patched
next reply other threads:[~2019-12-29 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 17:22 Paul Walmsley [this message]
2019-12-29 19:35 ` [GIT PULL] RISC-V updates for v5.5-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=alpine.DEB.2.21.9999.1912290921260.204131@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).