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-rc5
Date: Sat, 26 Oct 2019 17:02:43 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910261701250.12828@viisi.sifive.com> (raw)
Linus,
The following changes since commit 7d194c2100ad2a6dded545887d02754948ca5241:
Linux 5.4-rc4 (2019-10-20 15:56:22 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.4-rc5-b
for you to fetch changes up to e8f44c50dfe75315d1ff6efc837d62cbe7368c9b:
riscv: cleanup do_trap_break (2019-10-25 16:32:38 -0700)
----------------------------------------------------------------
RISC-V updates for v5.4-rc5
Several minor fixes and cleanups for v5.4-rc5:
- Three build fixes for various SPARSEMEM-related kernel configurations
- Two cleanup patches for the kernel bug and breakpoint trap handler code
----------------------------------------------------------------
Christoph Hellwig (2):
riscv: cleanup <asm/bug.h>
riscv: cleanup do_trap_break
David Abdurachmanov (1):
riscv: fix fs/proc/kcore.c compilation with sparsemem enabled
Kefeng Wang (2):
riscv: Fix implicit declaration of 'page_to_section'
riscv: Fix undefined reference to vmemmap_populate_basepages
arch/riscv/include/asm/bug.h | 16 +++-------------
arch/riscv/include/asm/pgtable.h | 7 +------
arch/riscv/kernel/traps.c | 26 ++++++--------------------
arch/riscv/mm/init.c | 2 +-
4 files changed, 11 insertions(+), 40 deletions(-)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-10-27 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 0:02 Paul Walmsley [this message]
2019-10-27 11:30 ` [GIT PULL] RISC-V updates for v5.4-rc5 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.1910261701250.12828@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).