Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Tomohiro Kusumi <kusumi.tomohiro@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH 1/7] Fix wrong cpuio option name in documentation
Date: Tue, 19 Jul 2016 15:47:26 -0600	[thread overview]
Message-ID: <20160719214726.GA27019@kernel.dk> (raw)
In-Reply-To: <1468946027-22580-1-git-send-email-kusumi.tomohiro@gmail.com>

On Wed, Jul 20 2016, Tomohiro Kusumi wrote:
> The name of an option for cpuio engine is "cpuchunks",
> though the code internally uses "cpucycle" for variables.
> 
> (If the option name "cpuchunks" is the incorrect one,
> I'll resubmit a patch that corrects the option name)

Thanks, applied all 7 patches.

-- 
Jens Axboe



  parent reply	other threads:[~2016-07-19 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 16:33 [PATCH 1/7] Fix wrong cpuio option name in documentation Tomohiro Kusumi
2016-07-19 16:33 ` [PATCH 2/7] Add CPU affinity support for DragonFlyBSD Tomohiro Kusumi
2016-07-19 16:33 ` [PATCH 3/7] Make I/O priority option generic for non-Linux environment [1/2] Tomohiro Kusumi
2016-07-19 16:33 ` [PATCH 4/7] Make I/O priority option generic for non-Linux environment [2/2] Tomohiro Kusumi
2016-07-19 16:33 ` [PATCH 5/7] Add ioprio_set() support for DragonFlyBSD Tomohiro Kusumi
2016-07-19 16:33 ` [PATCH 6/7] Change ARCH_X86_64_h to ARCH_X86_64_H Tomohiro Kusumi
2016-07-19 16:33 ` [PATCH 7/7] Add os/os-linux-syscall.h to separate syscall NR from arch headers Tomohiro Kusumi
2016-07-19 21:47 ` Jens Axboe [this message]
2016-07-19 22:20   ` [PATCH 1/7] Fix wrong cpuio option name in documentation Tomohiro Kusumi

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=20160719214726.GA27019@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=kusumi.tomohiro@gmail.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