From: Borislav Petkov <bp@alien8.de>
To: Lianbo Jiang <lijiang@redhat.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
akpm@linux-foundation.org, bhe@redhat.com, dyoung@redhat.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2 v3] kdump: add the vmcoreinfo documentation
Date: Mon, 17 Dec 2018 13:12:55 +0100 [thread overview]
Message-ID: <20181217121255.GC12165@zn.tnic> (raw)
In-Reply-To: <20181216131617.2612-2-lijiang@redhat.com>
On Sun, Dec 16, 2018 at 09:16:16PM +0800, Lianbo Jiang wrote:
This...
> +node_online_map
> +===============
> +It is a macro definition, actually it is an array node_states[N_ONLINE],
> +and it represents the set of online node in a system, one bit position
> +per node number.
> +
> +This is used to keep track of which nodes are in the system and online.
... and this...
> +nodemask_t
> +==========
> +The size of a 'nodemask_t' type. This value is used to compute the number
> +of online nodes.
sound redundant too?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-12-17 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 13:16 [PATCH 0/2 v3] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2018-12-16 13:16 ` [PATCH 1/2 v3] kdump: add the vmcoreinfo documentation Lianbo Jiang
2018-12-17 11:52 ` Borislav Petkov
2018-12-17 12:12 ` Borislav Petkov [this message]
2018-12-17 13:00 ` Borislav Petkov
2018-12-18 7:31 ` lijiang
2018-12-18 11:41 ` Borislav Petkov
2018-12-26 3:24 ` Dave Young
2018-12-26 3:36 ` Dave Young
2018-12-26 6:14 ` lijiang
2018-12-16 13:16 ` [PATCH 2/2 v3] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2018-12-17 13:01 ` Borislav Petkov
2018-12-18 7:34 ` lijiang
2018-12-17 11:54 ` [PATCH 0/2 " Borislav Petkov
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=20181217121255.GC12165@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).