IO-Uring Archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Cc: Ming Lei <ming.lei@redhat.com>
Subject: [PATCH V2 0/2] io_uring: support to inject result for NOP
Date: Fri, 10 May 2024 11:50:26 +0800	[thread overview]
Message-ID: <20240510035031.78874-1-ming.lei@redhat.com> (raw)

Hello,

The two patches add nop_flags for supporting to inject result on NOP.

V2:
	- add patch1 for backport, suggested by Jens


Ming Lei (2):
  io_uring: fail NOP if non-zero op flags is passed in
  io_uring: support to inject result for NOP

 include/uapi/linux/io_uring.h |  8 ++++++++
 io_uring/nop.c                | 26 ++++++++++++++++++++++----
 2 files changed, 30 insertions(+), 4 deletions(-)

-- 
2.42.0


             reply	other threads:[~2024-05-10  3:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  3:50 Ming Lei [this message]
2024-05-10  3:50 ` [PATCH V2 1/2] io_uring: fail NOP if non-zero op flags is passed in Ming Lei
2024-05-10  3:50 ` [PATCH V2 2/2] io_uring: support to inject result for NOP Ming Lei
2024-05-10 12:50 ` [PATCH V2 0/2] " 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 \
    --in-reply-to=20240510035031.78874-1-ming.lei@redhat.com \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).