From: Jonathan Corbet <corbet@lwn.net>
To: Baoquan He <bhe@redhat.com>
Cc: "Zhou, Wenjian/周文剑" <zhouwj-fnst@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
dyoung@redhat.com, vgoyal@redhat.com, kexec@lists.infradead.org,
linux-doc@vger.kernel.org, xlpang@redhat.com, joe@perches.com
Subject: Re: [PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus
Date: Thu, 25 Aug 2016 13:10:56 -0600 [thread overview]
Message-ID: <20160825131056.58bb1379@lwn.net> (raw)
In-Reply-To: <20160824050645.GA8279@x1.redhat.com>
On Wed, 24 Aug 2016 13:06:45 +0800
Baoquan He <bhe@redhat.com> wrote:
> Hi Jon, do you think change as below is OK to you?
So nr_cpus is the maximum value, and maxcpus is the current number.
Figures. No wonder the documentation is confusing...
Anyway, this is much more along the lines of what I was hoping for, yes;
I'll go ahead and apply it. Many thanks for humoring me on this!
jon
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Baoquan He <bhe@redhat.com>
Cc: linux-doc@vger.kernel.org, xlpang@redhat.com, "Zhou,
Wenjian/周文剑" <zhouwj-fnst@cn.fujitsu.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
joe@perches.com, akpm@linux-foundation.org, dyoung@redhat.com,
vgoyal@redhat.com
Subject: Re: [PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus
Date: Thu, 25 Aug 2016 13:10:56 -0600 [thread overview]
Message-ID: <20160825131056.58bb1379@lwn.net> (raw)
In-Reply-To: <20160824050645.GA8279@x1.redhat.com>
On Wed, 24 Aug 2016 13:06:45 +0800
Baoquan He <bhe@redhat.com> wrote:
> Hi Jon, do you think change as below is OK to you?
So nr_cpus is the maximum value, and maxcpus is the current number.
Figures. No wonder the documentation is confusing...
Anyway, this is much more along the lines of what I was hoping for, yes;
I'll go ahead and apply it. Many thanks for humoring me on this!
jon
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-08-25 19:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 3:11 [PATCH v9 0/2] update the doc of kdump Zhou Wenjian
2016-08-18 3:11 ` Zhou Wenjian
2016-08-18 3:11 ` [PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus Zhou Wenjian
2016-08-18 3:11 ` Zhou Wenjian
2016-08-18 17:18 ` Jonathan Corbet
2016-08-18 17:18 ` Jonathan Corbet
2016-08-19 0:33 ` "Zhou, Wenjian/周文剑"
2016-08-19 0:33 ` "Zhou, Wenjian/周文剑"
2016-08-19 15:57 ` Jonathan Corbet
2016-08-19 15:57 ` Jonathan Corbet
2016-08-22 1:14 ` "Zhou, Wenjian/周文剑"
2016-08-22 1:14 ` "Zhou, Wenjian/周文剑"
2016-08-24 5:06 ` Baoquan He
2016-08-24 5:06 ` Baoquan He
2016-08-25 19:10 ` Jonathan Corbet [this message]
2016-08-25 19:10 ` Jonathan Corbet
2016-08-27 0:35 ` Baoquan He
2016-08-27 0:35 ` Baoquan He
2016-08-26 0:45 ` "Zhou, Wenjian/周文剑"
2016-08-26 0:45 ` "Zhou, Wenjian/周文剑"
2016-08-27 0:38 ` Baoquan He
2016-08-27 0:38 ` Baoquan He
2016-08-18 3:11 ` [PATCH v9 2/2] Documentation: kdump: add description of enable multi-cpus support Zhou Wenjian
2016-08-18 3:11 ` 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=20160825131056.58bb1379@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=joe@perches.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.