All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dylan Yudaken <dylany@meta.com>
To: Jens Axboe <axboe@kernel.dk>, Pavel Begunkov <asml.silence@gmail.com>
Cc: <io-uring@vger.kernel.org>, <kernel-team@fb.com>,
	Dylan Yudaken <dylany@meta.com>
Subject: [PATCH for-next 0/3] io_uring: completion cleanups
Date: Fri, 25 Nov 2022 02:34:09 -0800	[thread overview]
Message-ID: <20221125103412.1425305-1-dylany@meta.com> (raw)

Hi,

A couple of tiny cleanups and 1 revert. I think the revert may be neater
if you just drop it from your tree.

Patch 1: small cleanup removing a not-needed
Patch 2: spelling fix
Patch 3: I think I merged this badly, or at least misunderstood the recent
changes. It was not needed, and confuses the _post suffix with also deferring.

Dylan Yudaken (3):
  io_uring: remove io_req_complete_post_tw
  io_uring: spelling fix
  io_uring: Revert "io_uring: io_req_complete_post should defer if
    available"

 io_uring/io_uring.c | 8 +++-----
 io_uring/io_uring.h | 7 -------
 2 files changed, 3 insertions(+), 12 deletions(-)


base-commit: 43f3ae1898c9c6d907e5b5c1887a90409ff7ad30
-- 
2.30.2


             reply	other threads:[~2022-11-25 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 10:34 Dylan Yudaken [this message]
2022-11-25 10:34 ` [PATCH for-next 1/3] io_uring: remove io_req_complete_post_tw Dylan Yudaken
2022-11-25 10:34 ` [PATCH for-next 2/3] io_uring: spelling fix Dylan Yudaken
2022-11-25 10:34 ` [PATCH for-next 3/3] io_uring: Revert "io_uring: io_req_complete_post should defer if available" Dylan Yudaken
2022-11-25 13:13 ` (subset) [PATCH for-next 0/3] io_uring: completion cleanups 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=20221125103412.1425305-1-dylany@meta.com \
    --to=dylany@meta.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kernel-team@fb.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.