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.8-rc7
Date: Sat, 25 Jul 2020 11:30:54 -0700 (PDT) [thread overview]
Message-ID: <mhng-f2bb3f7e-e2d6-48e5-a8f6-5e47edf5441e@palmerdabbelt-glaptop1> (raw)
The following changes since commit ba47d845d715a010f7b51f6f89bae32845e6acb7:
Linux 5.8-rc6 (2020-07-19 15:41:18 -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.8-rc7
for you to fetch changes up to fa5a198359053c8e21dcc2b39c0e13871059bc9f:
riscv: Parse all memory blocks to remove unusable memory (2020-07-24 22:08:25 -0700)
----------------------------------------------------------------
RISC-V Fixes for 5.8-rc7
I have a few more fixes this week:
* A fix to avoid using SBI calls during kasan initialization, as the SBI calls
themselves have not been probed yet.
* Three fixes related to systems with multiple memory regions.
----------------------------------------------------------------
Atish Patra (3):
RISC-V: Set maximum number of mapped pages correctly
RISC-V: Do not rely on initrd_start/end computed during early dt parsing
riscv: Parse all memory blocks to remove unusable memory
Vincent Chen (1):
riscv: kasan: use local_tlb_flush_all() to avoid uninitialized __sbi_rfence
arch/riscv/mm/init.c | 66 +++++++++++++++++++++++++++++++---------------
arch/riscv/mm/kasan_init.c | 4 +--
2 files changed, 47 insertions(+), 23 deletions(-)
next reply other threads:[~2020-07-25 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 18:30 Palmer Dabbelt [this message]
2020-07-25 22:30 ` [GIT PULL] RISC-V Fixes for 5.8-rc7 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-f2bb3f7e-e2d6-48e5-a8f6-5e47edf5441e@palmerdabbelt-glaptop1 \
--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).