From: Baoquan He <bhe@redhat.com>
To: corbet@lwn.net, akpm@linux-foundation.org
Cc: linux-doc@vger.kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, xlpang@redhat.com,
dyoung@redhat.com, Baoquan He <bhe@redhat.com>
Subject: [PATCH v10 RESEND 0/3] Documentation: Add description of enable multi-cpus support for kdump
Date: Mon, 19 Sep 2016 13:59:46 +0800 [thread overview]
Message-ID: <1474264789-11705-1-git-send-email-bhe@redhat.com> (raw)
This is v10 post. In this patchset patch 1/3 is added to give more details
about nr_cpus and maxcpus in kernel-parameters.txt. This is suggested by
Jonathan since the description of them is unclear so that people can't see
what's the exact difference between them. Otherwise no big further change
for 2/3 and 3/3 which comprise the old post.
Please access below link to check the previous changelog.
https://lkml.org/lkml/2016/8/17/646
Baoquan He (1):
docs: kernel-parameter : Improve the description of nr_cpus and
maxcpus
Zhou Wenjian (2):
Documentation: kdump: remind user of nr_cpus
Documentation: kdump: add description of enable multi-cpus support
Documentation/kdump/kdump.txt | 9 +++++++++
Documentation/kernel-parameters.txt | 20 +++++++++++++-------
2 files changed, 22 insertions(+), 7 deletions(-)
--
2.5.5
next reply other threads:[~2016-09-19 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 5:59 Baoquan He [this message]
2016-09-19 5:59 ` [PATCH v10 RESEND 1/3] docs: kernel-parameter : Improve the description of nr_cpus and maxcpus Baoquan He
2016-09-19 5:59 ` [PATCH v10 RESEND 2/3] Documentation: kdump: Remind user of nr_cpus Baoquan He
2016-09-19 5:59 ` [PATCH v10 RESEND 3/3] Documentation: kdump: Add description of enable multi-cpus support Baoquan He
2016-09-21 0:03 ` [PATCH v10 RESEND 0/3] Documentation: Add description of enable multi-cpus support for kdump Jonathan Corbet
2016-09-21 1:20 ` Baoquan He
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=1474264789-11705-1-git-send-email-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--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=xlpang@redhat.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 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).