From: Caleb Sander Mateos <csander@purestorage.com>
To: Anuj gupta <anuj1072538@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
io-uring@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] io_uring: add REQ_F_IOPOLL
Date: Thu, 19 Feb 2026 08:05:47 -0800 [thread overview]
Message-ID: <CADUfDZrk1Ro+VmaTDcbsUwQiL8EHhqbFbzHTrc5s0AJxbwdqTQ@mail.gmail.com> (raw)
In-Reply-To: <CACzX3AvpBv_vM5DNFmxBcMoCogC4HK1e0c58PA0kiBQ1wMacow@mail.gmail.com>
On Thu, Feb 19, 2026 at 4:39 AM Anuj gupta <anuj1072538@gmail.com> wrote:
>
> > REQ_F_HAS_METADATA_BIT,
> > REQ_F_IMPORT_BUFFER_BIT,
> > REQ_F_SQE_COPIED_BIT,
> > + REW_F_IOPOLL_BIT,
> >
> nit: should this be REQ_F_IOPOLL_BIT for naming consistency with the
> other REQ_F_*_BIT entries? Otherwise this looks good.
Absolutely, sorry for the typo.
Thanks,
Caleb
next prev parent reply other threads:[~2026-02-19 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260219014357epcas5p31a24ed7f17ebfe2d15f850c2a4114ebe@epcas5p3.samsung.com>
2026-02-19 1:43 ` [PATCH v2 0/4] io_uring/uring_cmd: allow non-iopoll cmds with IORING_SETUP_IOPOLL Caleb Sander Mateos
2026-02-19 1:43 ` [PATCH v2 1/4] io_uring: add REQ_F_IOPOLL Caleb Sander Mateos
2026-02-19 12:39 ` Anuj gupta
2026-02-19 16:05 ` Caleb Sander Mateos [this message]
2026-02-19 1:43 ` [PATCH v2 2/4] io_uring: remove iopoll_queue from struct io_issue_def Caleb Sander Mateos
2026-02-19 1:43 ` [PATCH v2 3/4] io_uring/uring_cmd: allow non-iopoll cmds with IORING_SETUP_IOPOLL Caleb Sander Mateos
2026-02-19 1:43 ` [PATCH v2 4/4] nvme: remove nvme_dev_uring_cmd() IO_URING_F_IOPOLL check Caleb Sander Mateos
2026-02-19 13:30 ` [PATCH v2 0/4] io_uring/uring_cmd: allow non-iopoll cmds with IORING_SETUP_IOPOLL Kanchan Joshi
2026-02-19 17:03 ` Caleb Sander Mateos
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=CADUfDZrk1Ro+VmaTDcbsUwQiL8EHhqbFbzHTrc5s0AJxbwdqTQ@mail.gmail.com \
--to=csander@purestorage.com \
--cc=anuj1072538@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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