From: Jens Axboe <[email protected]>
To: Keith Busch <[email protected]>, [email protected]
Subject: Re: [PATCH] fio: Use fixed opcodes for pre-mapped buffers
Date: Tue, 14 Jan 2020 14:27:41 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/14/20 2:24 PM, Keith Busch wrote:
> Use the correct opcode when for reads and writes using the fixedbuf
> option, otherwise EINVAL errors will be returned to these requests.
Oops, thanks for fixing!
--
Jens Axboe
prev parent reply other threads:[~2020-01-14 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 21:24 [PATCH] fio: Use fixed opcodes for pre-mapped buffers Keith Busch
2020-01-14 21:27 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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