From: Zhao Liu <zhao1.liu@linux.intel.com>
To: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Zhao Liu <zhao1.liu@intel.com>
Subject: Re: [RFC] docs/s390: Fix wrong command example in s390-cpu-topology.rst
Date: Mon, 27 Nov 2023 21:45:58 +0800 [thread overview]
Message-ID: <ZWSdlgfp50IuyHqd@intel.com> (raw)
In-Reply-To: <0c9271e79189edff10a85f99fe8a27ae287ad796.camel@linux.ibm.com>
Hi Nina,
On Mon, Nov 27, 2023 at 01:58:32PM +0100, Nina Schoetterl-Glausch wrote:
> Date: Mon, 27 Nov 2023 13:58:32 +0100
> From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> Subject: Re: [RFC] docs/s390: Fix wrong command example in
> s390-cpu-topology.rst
>
> On Mon, 2023-11-27 at 17:39 +0800, Zhao Liu wrote:
> > From: Zhao Liu <zhao1.liu@intel.com>
> >
> > From s390_possible_cpu_arch_ids() in hw/s390x/s390-virtio-ccw.c, the
> > "core-id" is the index of pssible_cpus->cpus[], so it should only be
>
> s/pssible_cpus/possible_cpus/
Thanks!
>
> > less than possible_cpus->len, which is equal to ms->smp.max_cpus.
> >
> > Fix the wrong "core-id" 112 because it is greater than maxcpus (36) in
>
> Maybe s/is greater/isn't less/ since the valid ids are 0-35 inclusive.
Ok.
>
> > -smp.
> >
> > Cc: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> > Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
>
> Reviewed-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Thanks! Let me refresh a new version quickly.
-Zhao
prev parent reply other threads:[~2023-11-27 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 9:39 [RFC] docs/s390: Fix wrong command example in s390-cpu-topology.rst Zhao Liu
2023-11-27 12:58 ` Nina Schoetterl-Glausch
2023-11-27 13:45 ` Zhao Liu [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=ZWSdlgfp50IuyHqd@intel.com \
--to=zhao1.liu@linux.intel.com \
--cc=nsg@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=zhao1.liu@intel.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.