From: Karel Zak <kzak@redhat.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: util-linux@vger.kernel.org, heiko.carstens@de.ibm.com, kerolasa@iki.fi
Subject: Re: [PATCH RESEND] lscpu: Fix issue found on CPU hot-remove
Date: Mon, 5 Nov 2012 19:56:14 +0100 [thread overview]
Message-ID: <20121105185614.GF3799@x2.net.home> (raw)
In-Reply-To: <1352135015-13946-1-git-send-email-toshi.kani@hp.com>
On Mon, Nov 05, 2012 at 10:03:35AM -0700, Toshi Kani wrote:
> read_basicinfo() relies on sysfs cpu directories
> "/sys/devices/system/cpu/cpu%d" with assumption that cpu
> logical number %d is always sequentially assigned for all
Ah, sorry I have moved the mail to my mail archive without response...
thanks for resend.
It seems correct, I'll apply the patch tomorrow.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-11-05 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 17:03 [PATCH RESEND] lscpu: Fix issue found on CPU hot-remove Toshi Kani
2012-11-05 18:56 ` Karel Zak [this message]
2012-11-05 19:16 ` Toshi Kani
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=20121105185614.GF3799@x2.net.home \
--to=kzak@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kerolasa@iki.fi \
--cc=toshi.kani@hp.com \
--cc=util-linux@vger.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