From: Anup Patel <anup@brainfault.org>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
Atish Patra <atish.patra@wdc.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [GIT PULL] Second set of RISC-V updates for v5.5-rc1
Date: Wed, 4 Dec 2019 18:22:06 +0530 [thread overview]
Message-ID: <CAAhSdy2id0FoLBxWwN7WHEk5Am770BizkK=sZO0-G54MtYa6DQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1912040050430.56420@viisi.sifive.com>
On Wed, Dec 4, 2019 at 2:22 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> 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
I had commented on your patch but my comments are still
not addressed.
Various debug options enabled by this patch have performance
impact. Instead of enabling these debug options in primary
defconfigs, I suggest to have separate debug defconfigs with
these options enabled.
Please address my comments and send this patch in
separate PR.
Regards,
Anup
> 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 prev parent reply other threads:[~2019-12-04 12:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:52 [GIT PULL] Second set of RISC-V updates for v5.5-rc1 Paul Walmsley
2019-12-04 12:52 ` Anup Patel [this message]
2019-12-04 18:38 ` Alistair Francis
2019-12-04 19:38 ` Paul Walmsley
2019-12-04 19:50 ` Alistair Francis
2019-12-04 23:46 ` Anup Patel
2019-12-05 2:54 ` Paul Walmsley
2019-12-05 3:58 ` Alistair Francis
2019-12-05 5:35 ` David Abdurachmanov
2019-12-05 13:19 ` Anup Patel
2019-12-05 23:12 ` Paul Walmsley
2019-12-05 23:35 ` Alistair Francis
2019-12-05 23:46 ` Alistair Francis
2019-12-06 21:12 ` Carlos Eduardo de Paula
2019-12-06 21:15 ` Anup Patel
2019-12-06 21:21 ` Carlos Eduardo de Paula
2019-12-06 21:22 ` Linus Torvalds
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='CAAhSdy2id0FoLBxWwN7WHEk5Am770BizkK=sZO0-G54MtYa6DQ@mail.gmail.com' \
--to=anup@brainfault.org \
--cc=Alistair.Francis@wdc.com \
--cc=atish.patra@wdc.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
--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).