From: Jonathan Corbet <corbet@lwn.net>
To: Baoquan He <bhe@redhat.com>
Cc: linux-doc@vger.kernel.org, kexec@lists.infradead.org,
xlpang@redhat.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, dyoung@redhat.com
Subject: Re: [PATCH v10 RESEND 0/3] Documentation: Add description of enable multi-cpus support for kdump
Date: Tue, 20 Sep 2016 18:03:46 -0600 [thread overview]
Message-ID: <20160920180346.595fd720@lwn.net> (raw)
In-Reply-To: <1474264789-11705-1-git-send-email-bhe@redhat.com>
On Mon, 19 Sep 2016 13:59:46 +0800
Baoquan He <bhe@redhat.com> wrote:
> 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.
So somehow I'd applied 1/3 a while back, but not the other two. All three
are in the docs tree now, thanks.
jon
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Baoquan He <bhe@redhat.com>
Cc: akpm@linux-foundation.org, linux-doc@vger.kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
xlpang@redhat.com, dyoung@redhat.com
Subject: Re: [PATCH v10 RESEND 0/3] Documentation: Add description of enable multi-cpus support for kdump
Date: Tue, 20 Sep 2016 18:03:46 -0600 [thread overview]
Message-ID: <20160920180346.595fd720@lwn.net> (raw)
In-Reply-To: <1474264789-11705-1-git-send-email-bhe@redhat.com>
On Mon, 19 Sep 2016 13:59:46 +0800
Baoquan He <bhe@redhat.com> wrote:
> 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.
So somehow I'd applied 1/3 a while back, but not the other two. All three
are in the docs tree now, thanks.
jon
next prev parent reply other threads:[~2016-09-21 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 5:59 [PATCH v10 RESEND 0/3] Documentation: Add description of enable multi-cpus support for kdump Baoquan He
2016-09-19 5:59 ` Baoquan He
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 ` 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 ` 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-19 5:59 ` Baoquan He
2016-09-21 0:03 ` Jonathan Corbet [this message]
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
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=20160920180346.595fd720@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--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 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.