From: Sachin Sant <sachinp@linux.ibm.com>
To: Martin Doucha <mdoucha@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/3] io_uring: Test IORING READ and WRITE operations
Date: Thu, 16 Apr 2026 15:06:17 +0530 [thread overview]
Message-ID: <d41449ae-b898-4ee5-b067-b8ff1cf5c836@linux.ibm.com> (raw)
In-Reply-To: <b02c247c-94ed-4960-94c2-da62b2f5a474@suse.cz>
On 16/04/26 2:25 pm, Martin Doucha wrote:
> On 3/24/26 06:22, Sachin Sant wrote:
>> +/*
>> + * Map io_uring operation code to human-readable name
>> + */
>> +static inline const char *ioring_op_name(int op)
>> +{
>> + switch (op) {
>> + case IORING_OP_READV:
>> + return "IORING_OP_READV";
>> + case IORING_OP_WRITEV:
>> + return "IORING_OP_WRITEV";
>> + case IORING_OP_READ:
>> + return "IORING_OP_READ";
>> + case IORING_OP_WRITE:
>> + return "IORING_OP_WRITE";
>
> Hi,
> IORING_OP_READ and IORING_OP_WRITE have been added in kernel v5.6.
> Some older distros currently fail to build LTP due to their missing
> declarations so you'll need to add those constants to lapi headers.
>
Thank you for the report. I will send a fix to address this.
--
Thanks
- Sachin
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-16 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 5:22 [LTP] [PATCH v2 0/3] io_uring READ(V), WRITE(v) operation tests Sachin Sant
2026-03-24 5:22 ` [LTP] [PATCH v2 1/3] io_uring: Test IORING READ and WRITE operations Sachin Sant
2026-04-16 8:55 ` Martin Doucha
2026-04-16 9:36 ` Sachin Sant [this message]
2026-03-24 5:22 ` [LTP] [PATCH v2 2/3] io_uring: Test READV and WRITEV operations Sachin Sant
2026-04-15 9:59 ` Cyril Hrubis
2026-04-15 13:56 ` Sachin Sant
2026-03-24 5:22 ` [LTP] [PATCH v2 3/3] io_uring: Refactor io_uring01 to use common code Sachin Sant
2026-04-15 9:35 ` [LTP] [PATCH v2 0/3] io_uring READ(V), WRITE(v) operation tests Cyril Hrubis
2026-04-15 13:58 ` Sachin Sant
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=d41449ae-b898-4ee5-b067-b8ff1cf5c836@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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