From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
"Wei, Gang" <gang.wei@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xenpm: fix get-cpu-topology
Date: Mon, 12 Jul 2010 18:19:41 +0100 [thread overview]
Message-ID: <C8610D3D.1A716%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <19515.19345.639405.425265@mariner.uk.xensource.com>
On 12/07/2010 18:06, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> * The size of this array is specified by the caller in @max_cpu_index.
> * If the actual @max_cpu_index is smaller than the array then the
> trailing
> * elements of the array will not be written by the sysctl.
> */
>
> So is it the size of the array or the maximum index ?
It's the maximum index. Pedantically, that is sufficient to specify the size
of the array. It is unnecessarily confusing wording though.
-- Keir
prev parent reply other threads:[~2010-07-12 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 10:58 xenpm: fix get-cpu-topology Wei, Gang
2010-07-12 17:06 ` Ian Jackson
2010-07-12 17:19 ` Keir Fraser [this message]
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=C8610D3D.1A716%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=gang.wei@intel.com \
--cc=xen-devel@lists.xensource.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).