From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH liburing] convert buf-ring nop test to use read
Date: Wed, 15 Jun 2022 15:24:53 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, 15 Jun 2022 04:37:33 -0700, Dylan Yudaken wrote:
> The NOP support for IOSQE_BUFFER_SELECT has been reverted, so use a
> supported function with read. This also allows verifying that the
> correct data has actually been read.
>
>
Applied, thanks!
[1/1] convert buf-ring nop test to use read
commit: 649d7468ffc2903ca659e976c134e5602e4810bc
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-15 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 11:37 [PATCH liburing] convert buf-ring nop test to use read Dylan Yudaken
2022-06-15 21:24 ` 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=165532829344.853523.15656103547403478325.b4-ty@kernel.dk \
[email protected] \
[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