From: "long.wanglong" <long.wanglong@huawei.com>
To: Wang Long <long.wanglong@huawei.com>, <vegard.nossum@gmail.com>
Cc: <vegardno@ifi.uio.no>, <penberg@kernel.org>, <corbet@lwn.net>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<peifeiyue@huawei.com>
Subject: Re: [PATCH] Documentation: update the CONFIG_DEBUG_PAGEALLOC description
Date: Wed, 11 Mar 2015 11:38:08 +0800 [thread overview]
Message-ID: <54FFB8A0.5020408@huawei.com> (raw)
In-Reply-To: <1425281320-33476-1-git-send-email-long.wanglong@huawei.com>
On 2015/3/2 15:28, Wang Long wrote:
cc: vegard.nossum@gmail.com
> The CONFIG_DEBUG_PAGEALLOC option now is located under "Kernel
> hacking" / "Memory Debugging" / "Debug page memory allocations".
> so we should update the description in kmemcheck.txt.
>
> Signed-off-by: Wang Long <long.wanglong@huawei.com>
> ---
> Documentation/kmemcheck.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/kmemcheck.txt b/Documentation/kmemcheck.txt
> index a41bdeb..80aae85 100644
> --- a/Documentation/kmemcheck.txt
> +++ b/Documentation/kmemcheck.txt
> @@ -82,8 +82,8 @@ menu to even appear in "menuconfig". These are:
>
> o CONFIG_DEBUG_PAGEALLOC=n
>
> - This option is located under "Kernel hacking" / "Debug page memory
> - allocations".
> + This option is located under "Kernel hacking" / "Memory Debugging"
> + / "Debug page memory allocations".
>
> In addition, I highly recommend turning on CONFIG_DEBUG_INFO=y. This is also
> located under "Kernel hacking". With this, you will be able to get line number
>
next prev parent reply other threads:[~2015-03-11 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 7:28 Wang Long
2015-03-11 3:38 ` long.wanglong [this message]
2015-03-19 20:47 ` Jonathan Corbet
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=54FFB8A0.5020408@huawei.com \
--to=long.wanglong@huawei.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peifeiyue@huawei.com \
--cc=penberg@kernel.org \
--cc=vegard.nossum@gmail.com \
--cc=vegardno@ifi.uio.no \
/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
Powered by JetHome