From: Palmer Dabbelt <palmer@dabbelt.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.12-rc8 (or 5.12)
Date: Fri, 16 Apr 2021 09:57:52 -0700 (PDT) [thread overview]
Message-ID: <mhng-769b7cf7-7dfb-455a-9bb3-99f5cd952dbe@palmerdabbelt-glaptop> (raw)
The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120:
Linux 5.12-rc6 (2021-04-04 14:15:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.12-rc8
for you to fetch changes up to 7ae11635ec90072083503c6b6485cdffe46203b3:
riscv: keep interrupts disabled for BREAKPOINT exception (2021-04-15 21:32:40 -0700)
----------------------------------------------------------------
RISC-V Fixes for 5.12-rc8 (or 5.12)
I have a handful of fixes that I'd like to target for 5.12, regardless
of whether there's an rc8 or not:
* A fix to properly select SPARSEMEM_STATIC on rv32.
* A handful of fixes to kprobes.
I don't generally like sending stuff this late, but these all seem
pretty safe.
----------------------------------------------------------------
Jisheng Zhang (3):
riscv: add do_page_fault and do_trap_break into the kprobes blacklist
riscv: kprobes/ftrace: Add recursion protection to the ftrace callback
riscv: keep interrupts disabled for BREAKPOINT exception
Kefeng Wang (1):
riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
arch/riscv/Kconfig | 2 +-
arch/riscv/kernel/entry.S | 3 +++
arch/riscv/kernel/probes/ftrace.c | 11 ++++++++++-
arch/riscv/kernel/traps.c | 1 +
arch/riscv/mm/fault.c | 1 +
5 files changed, 16 insertions(+), 2 deletions(-)
next reply other threads:[~2021-04-16 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 16:57 Palmer Dabbelt [this message]
2021-04-16 17:08 ` [GIT PULL] RISC-V Fixes for 5.12-rc8 (or 5.12) 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=mhng-769b7cf7-7dfb-455a-9bb3-99f5cd952dbe@palmerdabbelt-glaptop \
--to=palmer@dabbelt.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).