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.4-rc3
Date: Sat, 12 Oct 2019 13:10:52 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910121307270.18026@viisi.sifive.com> (raw)
Linus,
The following changes since commit da0c9ea146cbe92b832f1b0f694840ea8eb33cce:
Linux 5.4-rc2 (2019-10-06 14:27:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.4-rc3
for you to fetch changes up to cd9e72b80090a8cd7d84a47a30a06fa92ff277d1:
RISC-V: entry: Remove unneeded need_resched() loop (2019-10-09 16:48:27 -0700)
----------------------------------------------------------------
RISC-V updates for v5.4-rc3
Some RISC-V fixes for v5.4-rc3:
- Fix several bugs in the breakpoint trap handler
- Drop an unnecessary loop around calls to preempt_schedule_irq()
----------------------------------------------------------------
Valentin Schneider (1):
RISC-V: entry: Remove unneeded need_resched() loop
Vincent Chen (3):
riscv: avoid kernel hangs when trapped in BUG()
riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()
riscv: Correct the handling of unexpected ebreak in do_trap_break()
arch/riscv/kernel/entry.S | 3 +--
arch/riscv/kernel/traps.c | 14 +++++++-------
2 files changed, 8 insertions(+), 9 deletions(-)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-10-12 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 20:10 Paul Walmsley [this message]
2019-10-12 21:40 ` [GIT PULL] RISC-V updates for v5.4-rc3 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.1910121307270.18026@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).