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] Second set of RISC-V updates for v5.5-rc1
Date: Wed, 4 Dec 2019 00:52:08 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1912040050430.56420@viisi.sifive.com> (raw)
Linus,
The following changes since commit 5ba9aa56e6d3e8fddb954c2f818d1ce0525235bb:
Merge branch 'next/nommu' into for-next (2019-11-22 18:59:09 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.5-rc1-2
for you to fetch changes up to 1646220a6d4b27153ddb5ffb117aa1f4c39e3d1f:
Merge branch 'next/defconfig-add-debug' into for-next (2019-11-22 18:59:23 -0800)
----------------------------------------------------------------
Second set of RISC-V updates for v5.5-rc1
A few minor RISC-V updates for v5.5-rc1 that arrived late.
New features:
- Dump some kernel virtual memory map details to the console if
CONFIG_DEBUG_VM is enabled
Other improvements:
- Enable more debugging options in the primary defconfigs
Cleanups:
- Clean up Kconfig indentation
----------------------------------------------------------------
Krzysztof Kozlowski (1):
riscv: Fix Kconfig indentation
Paul Walmsley (4):
riscv: defconfigs: enable debugfs
riscv: defconfigs: enable more debugging options
Merge branch 'next/misc2' into for-next
Merge branch 'next/defconfig-add-debug' into for-next
Yash Shah (1):
RISC-V: Add address map dumper
arch/riscv/Kconfig.socs | 16 ++++++++--------
arch/riscv/configs/defconfig | 24 ++++++++++++++++++++++++
arch/riscv/configs/rv32_defconfig | 24 ++++++++++++++++++++++++
arch/riscv/mm/init.c | 32 ++++++++++++++++++++++++++++++++
4 files changed, 88 insertions(+), 8 deletions(-)
next reply other threads:[~2019-12-04 8:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:52 Paul Walmsley [this message]
2019-12-04 12:52 ` [GIT PULL] Second set of RISC-V updates for v5.5-rc1 Anup Patel
2019-12-04 12:52 ` Anup Patel
2019-12-04 18:38 ` Alistair Francis
2019-12-04 18:38 ` Alistair Francis
2019-12-04 19:38 ` Paul Walmsley
2019-12-04 19:38 ` Paul Walmsley
2019-12-04 19:50 ` Alistair Francis
2019-12-04 19:50 ` Alistair Francis
2019-12-04 23:46 ` Anup Patel
2019-12-04 23:46 ` Anup Patel
2019-12-05 2:54 ` Paul Walmsley
2019-12-05 2:54 ` Paul Walmsley
2019-12-05 3:58 ` Alistair Francis
2019-12-05 3:58 ` Alistair Francis
2019-12-05 5:35 ` David Abdurachmanov
2019-12-05 5:35 ` David Abdurachmanov
2019-12-05 13:19 ` Anup Patel
2019-12-05 13:19 ` Anup Patel
2019-12-05 23:12 ` Paul Walmsley
2019-12-05 23:12 ` Paul Walmsley
2019-12-05 23:35 ` Alistair Francis
2019-12-05 23:35 ` Alistair Francis
2019-12-05 23:46 ` Alistair Francis
2019-12-05 23:46 ` Alistair Francis
2019-12-06 21:12 ` Carlos Eduardo de Paula
2019-12-06 21:12 ` Carlos Eduardo de Paula
2019-12-06 21:15 ` Anup Patel
2019-12-06 21:15 ` Anup Patel
2019-12-06 21:21 ` Carlos Eduardo de Paula
2019-12-06 21:21 ` Carlos Eduardo de Paula
2019-12-06 21:22 ` Linus Torvalds
2019-12-06 21:22 ` Linus Torvalds
2019-12-04 19:25 ` pr-tracker-bot
2019-12-04 19:25 ` 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.1912040050430.56420@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.