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-rc2
Date: Fri, 4 Oct 2019 10:36:54 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910041036010.15827@viisi.sifive.com> (raw)
Linus,
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -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-rc2
for you to fetch changes up to 922b0375fc93fb1a20c5617e37c389c26bbccb70:
riscv: Fix memblock reservation for device tree blob (2019-10-01 13:22:39 -0700)
----------------------------------------------------------------
RISC-V updates for v5.4-rc2
Two RISC-V fixes for v5.4-rc2:
- Ensure that exclusive-load reservations are terminated after system
call or exception handling. This primarily affects QEMU, which does
not expire load reservations.
- Fix an issue primarily affecting RV32 platforms that can cause the
DT header to be corrupted, causing boot failures.
----------------------------------------------------------------
Albert Ou (1):
riscv: Fix memblock reservation for device tree blob
Palmer Dabbelt (1):
RISC-V: Clear load reservations while restoring hart contexts
arch/riscv/include/asm/asm.h | 1 +
arch/riscv/kernel/entry.S | 21 ++++++++++++++++++++-
arch/riscv/mm/init.c | 12 +++++++++++-
3 files changed, 32 insertions(+), 2 deletions(-)
next reply other threads:[~2019-10-04 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 17:36 Paul Walmsley [this message]
2019-10-04 20:26 ` [GIT PULL] RISC-V updates for v5.4-rc2 Linus Torvalds
2019-10-04 20:40 ` 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.1910041036010.15827@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).