public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, peterz@infradead.org,
	andres@anarazel.de
Subject: Re: [PATCHSET v2 0/8] Add io_uring futex/futexv support
Date: Wed, 12 Jul 2023 10:58:51 -0600	[thread overview]
Message-ID: <624160ca-ccea-0389-6e17-2dd2daf1451d@kernel.dk> (raw)
In-Reply-To: <20230712162017.391843-1-axboe@kernel.dk>


Neglected to mention, that I have run this through the ltp futex tests,
and there are no changes. All tests pass.

-- 
Jens Axboe


      parent reply	other threads:[~2023-07-12 16:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 16:20 [PATCHSET v2 0/8] Add io_uring futex/futexv support Jens Axboe
2023-07-12 16:20 ` [PATCH 1/8] futex: abstract out futex_op_to_flags() helper Jens Axboe
2023-07-12 16:20 ` [PATCH 2/8] futex: factor out the futex wake handling Jens Axboe
2023-07-12 16:20 ` [PATCH 3/8] futex: abstract out a __futex_wake_mark() helper Jens Axboe
2023-07-12 16:20 ` [PATCH 4/8] io_uring: add support for futex wake and wait Jens Axboe
2023-07-13 11:15   ` Peter Zijlstra
2023-07-13 16:25     ` Jens Axboe
2023-07-13 17:24     ` Peter Zijlstra
2023-07-14 14:52       ` Jens Axboe
2023-07-14 15:08         ` Peter Zijlstra
2023-07-14 15:10           ` Jens Axboe
2023-07-12 16:20 ` [PATCH 5/8] futex: add wake_data to struct futex_q Jens Axboe
2023-07-12 16:20 ` [PATCH 6/8] futex: make futex_parse_waitv() available as a helper Jens Axboe
2023-07-12 16:20 ` [PATCH 7/8] futex: make the vectored futex operations available Jens Axboe
2023-07-12 16:20 ` [PATCH 8/8] io_uring: add support for vectored futex waits Jens Axboe
2023-07-13 11:54   ` Peter Zijlstra
2023-07-13 16:26     ` Jens Axboe
2023-07-12 16:58 ` Jens Axboe [this message]

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=624160ca-ccea-0389-6e17-2dd2daf1451d@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=andres@anarazel.de \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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