From: Kanchan Joshi <[email protected]>
To: [email protected]
Cc: [email protected], Kanchan Joshi <[email protected]>
Subject: [PATCH liburing 2/2] test/io_uring_passthrough: cleanup invalid submission test
Date: Tue, 6 Dec 2022 17:48:31 +0530 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Just do away with setting IOPOLL as this is not necessary for the test.
Signed-off-by: Kanchan Joshi <[email protected]>
---
test/io_uring_passthrough.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/test/io_uring_passthrough.c b/test/io_uring_passthrough.c
index b58feae..7efdba1 100644
--- a/test/io_uring_passthrough.c
+++ b/test/io_uring_passthrough.c
@@ -286,8 +286,7 @@ static int test_invalid_passthru_submit(const char *file)
struct io_uring_sqe *sqe;
struct nvme_uring_cmd *cmd;
- ring_flags = IORING_SETUP_IOPOLL | IORING_SETUP_SQE128;
- ring_flags |= IORING_SETUP_CQE32;
+ ring_flags = IORING_SETUP_CQE32 | IORING_SETUP_SQE128;
ret = t_create_ring(1, &ring, ring_flags);
if (ret != T_SETUP_OK) {
--
2.25.1
next prev parent reply other threads:[~2022-12-06 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221206123005epcas5p474a1374f850c47f2c9af5ef8c8cc6509@epcas5p4.samsung.com>
2022-12-06 12:18 ` [PATCH liburing 0/2] passthrough test fix and cleanup Kanchan Joshi
[not found] ` <CGME20221206123009epcas5p4d65eca3320f9845e190fc425a06799a6@epcas5p4.samsung.com>
2022-12-06 12:18 ` [PATCH liburing 1/2] test/io_uring_passthrough: fix iopoll test Kanchan Joshi
[not found] ` <CGME20221206123012epcas5p33de3600bbc6effa8e2a08f748cb0eee4@epcas5p3.samsung.com>
2022-12-06 12:18 ` Kanchan Joshi [this message]
2022-12-06 17:19 ` [PATCH liburing 0/2] passthrough test fix and cleanup Jens Axboe
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