* [PATCH] io_uring: Add {} to maintain consistency in code format
@ 2023-06-30 6:25 Lu Hongfei
0 siblings, 0 replies; only message in thread
From: Lu Hongfei @ 2023-06-30 6:25 UTC (permalink / raw)
To: Jens Axboe, Pavel Begunkov, io-uring, linux-kernel
Cc: opensource.kernel, luhongfei
In io_issue_sqe, the if (ret == IOU_OK) branch uses {}, so to maintain code
format consistency, it is better to add {} in the else branch.
Signed-off-by: Lu Hongfei <[email protected]>
---
io_uring/io_uring.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index e8096d502a7c..335ba8d49d74 100644
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -1877,8 +1877,9 @@ static int io_issue_sqe(struct io_kiocb *req, unsigned int issue_flags)
io_req_complete_defer(req);
else
io_req_complete_post(req, issue_flags);
- } else if (ret != IOU_ISSUE_SKIP_COMPLETE)
+ } else if (ret != IOU_ISSUE_SKIP_COMPLETE) {
return ret;
+ }
/* If the op doesn't have a file, we're not polling for it */
if ((req->ctx->flags & IORING_SETUP_IOPOLL) && def->iopoll_queue)
--
2.39.0
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2023-06-30 6:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-30 6:25 [PATCH] io_uring: Add {} to maintain consistency in code format Lu Hongfei
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox