From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@wdc.com>, fio <fio@vger.kernel.org>
Subject: Re: [PATCH] fix windows cpu count
Date: Fri, 2 Nov 2018 10:54:37 -0600 [thread overview]
Message-ID: <dd487a15-5bf3-1f0b-c8af-c625e322b625@kernel.dk> (raw)
In-Reply-To: <MWHPR04MB03206DB9864943065BA28C218FCF0@MWHPR04MB0320.namprd04.prod.outlook.com>
On 11/2/18 10:44 AM, Jeff Furlong wrote:
> This patch resolves c479640d6208236744f0562b1e79535eec290e2b where the
> CPU count returns max possible supported CPUs, and instead returns
> current active CPUs.
I'd like to apply this patch, but your mailer has completely
botched it up. It's damaging white space (turning tabs into
spaces), and breaking up lines that it thinks are too long.
--
Jens Axboe
prev parent reply other threads:[~2018-11-02 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 16:44 [PATCH] fix windows cpu count Jeff Furlong
2018-11-02 16:54 ` Jens Axboe [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=dd487a15-5bf3-1f0b-c8af-c625e322b625@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=jeff.furlong@wdc.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.