From: Joe Perches <joe@perches.com>
To: Zhou Wenjian <zhouwj-fnst@cn.fujitsu.com>, linux-kernel@vger.kernel.org
Cc: bhe@redhat.com, corbet@lwn.net, xlpang@redhat.com,
linux-doc@vger.kernel.org, kexec@lists.infradead.org,
akpm@linux-foundation.org, dyoung@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus
Date: Wed, 17 Aug 2016 19:36:49 -0700 [thread overview]
Message-ID: <1471487809.4319.15.camel@perches.com> (raw)
In-Reply-To: <1471487495-22787-2-git-send-email-zhouwj-fnst@cn.fujitsu.com>
On Thu, 2016-08-18 at 10:31 +0800, Zhou Wenjian wrote:
> nr_cpus can help to save memory. So we should remind user of it.
trivia:
> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
[]
> @@ -390,9 +390,11 @@ Notes on loading the dump-capture kernel:
> * Boot parameter "1" boots the dump-capture kernel into single-user
> mode without networking. If you want networking, use "3".
>
> -* We generally don' have to bring up a SMP kernel just to capture the
> +* We generally don' have to bring up an SMP kernel just to capture the
don't or do not
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Zhou Wenjian <zhouwj-fnst@cn.fujitsu.com>, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, dyoung@redhat.com, bhe@redhat.com,
vgoyal@redhat.com, corbet@lwn.net, kexec@lists.infradead.org,
linux-doc@vger.kernel.org, xlpang@redhat.com
Subject: Re: [PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus
Date: Wed, 17 Aug 2016 19:36:49 -0700 [thread overview]
Message-ID: <1471487809.4319.15.camel@perches.com> (raw)
In-Reply-To: <1471487495-22787-2-git-send-email-zhouwj-fnst@cn.fujitsu.com>
On Thu, 2016-08-18 at 10:31 +0800, Zhou Wenjian wrote:
> nr_cpus can help to save memory. So we should remind user of it.
trivia:
> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
[]
> @@ -390,9 +390,11 @@ Notes on loading the dump-capture kernel:
> * Boot parameter "1" boots the dump-capture kernel into single-user
> mode without networking. If you want networking, use "3".
>
> -* We generally don' have to bring up a SMP kernel just to capture the
> +* We generally don' have to bring up an SMP kernel just to capture the
don't or do not
next prev parent reply other threads:[~2016-08-18 2:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 2:31 [PATCH v8 0/2] update the doc of kdump Zhou Wenjian
2016-08-18 2:31 ` Zhou Wenjian
2016-08-18 2:31 ` [PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus Zhou Wenjian
2016-08-18 2:31 ` Zhou Wenjian
2016-08-18 2:36 ` Joe Perches [this message]
2016-08-18 2:36 ` Joe Perches
2016-08-18 6:47 ` Dave Young
2016-08-18 6:47 ` Dave Young
2016-08-18 7:12 ` "Zhou, Wenjian/周文剑"
2016-08-18 7:12 ` "Zhou, Wenjian/周文剑"
2016-08-18 2:31 ` [PATCH v8 2/2] Documentation: kdump: add description of enable multi-cpus support Zhou Wenjian
2016-08-18 2:31 ` Zhou Wenjian
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=1471487809.4319.15.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=xlpang@redhat.com \
--cc=zhouwj-fnst@cn.fujitsu.com \
/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.