From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: mm: Enhance Virtual kernel memory layout
Date: Fri, 15 Apr 2016 18:20:48 +0100 [thread overview]
Message-ID: <20160415172047.GA8490@arm.com> (raw)
In-Reply-To: <1460533772-13314-1-git-send-email-wangkefeng.wang@huawei.com>
Hi Kefeng,
On Wed, Apr 13, 2016 at 03:49:32PM +0800, Kefeng Wang wrote:
> 1) Show kernel excetion vector region and bss segment information.
> 2) Only show modules and PCI I/O with corresponding config enabled.
> 3) Each line with single pr_cont, or lead to anomalous print in dmesg.
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
Can you post a new version of this patch addressing James's feedback,
please?
Thanks,
Will
next prev parent reply other threads:[~2016-04-15 17:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 7:49 [PATCH] arm64: mm: Enhance Virtual kernel memory layout Kefeng Wang
2016-04-13 9:26 ` James Morse
2016-04-14 6:57 ` Kefeng Wang
2016-04-15 17:20 ` Will Deacon [this message]
2016-04-18 2:05 ` Kefeng Wang
2016-04-18 3:09 ` [PATCH v2 0/3] " Kefeng Wang
2016-04-18 3:09 ` [PATCH v2 1/3] arm64: mm: make pr_cont() per line in " Kefeng Wang
2016-04-18 11:16 ` James Morse
2016-04-18 11:21 ` Ard Biesheuvel
2016-04-18 13:13 ` James Morse
2016-04-19 5:58 ` Kefeng Wang
2016-04-18 3:09 ` [PATCH v2 2/3] arm64: mm: Show bss segment in " Kefeng Wang
2016-04-18 11:14 ` James Morse
2016-04-18 3:09 ` [PATCH v2 3/3] arm64: mm: Restrictive printing for modules and PCI I/O in " Kefeng Wang
2016-04-18 11:15 ` James Morse
2016-04-19 7:08 ` Kefeng Wang
2016-05-12 12:16 ` [PATCH v3 0/2] arm64: mm: Enhance Virtual kernel " Kefeng Wang
2016-05-12 12:16 ` [PATCH v3 1/2] arm64: mm: make pr_cont() per line in " Kefeng Wang
2016-05-12 12:16 ` [PATCH v3 2/2] arm64: mm: Show bss segment in " Kefeng Wang
2016-05-12 13:36 ` [PATCH v3 0/2] arm64: mm: Enhance Virtual " Will Deacon
2016-05-13 1:21 ` Kefeng Wang
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=20160415172047.GA8490@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).