public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Linux Kernel Mailing List <[email protected]>,
	Kanna Scarlet <[email protected]>,
	Caleb Sander <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Muhammad Rizki <[email protected]>,
	io-uring Mailing List <[email protected]>
Subject: Re: [PATCH liburing v2 0/7] Export io_uring syscall functions
Date: Tue, 30 Aug 2022 08:14:38 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Tue, 30 Aug 2022 07:56:36 +0700, Ammar Faizi wrote:
> From: Ammar Faizi <[email protected]>
> 
> Hi Jens,
> 
> This series adds io_uring syscall functions and exports them. There
> are 7 patches in this series:
> 
> [...]

Applied, thanks!

[1/7] syscall: Make io_uring syscall arguments consistent
      commit: 09164272d3aa5f4727fdf2181284d29e88194201
[2/7] syscall: Add io_uring syscall functions
      commit: f0b43c84cb3d1a4af4f1a32193bcad66fe458488
[3/7] man: Clarify "man 2" entry for io_uring syscalls
      commit: 9a8512f6dbd259a52b3f98fb5e6324a9b2841c3c
[4/7] man: Add `io_uring_enter2()` function signature
      commit: 584b9ed0ceef30934e747435fe0b535528495de6
[5/7] man: Alias `io_uring_enter2()` to `io_uring_enter()`
      commit: 8251e2778b0a1a897337aa011cb59ec85de599e0
[6/7] test/io_uring_{enter,setup,register}: Use the exported syscall functions
      commit: 64208a184c155580bfde12ced79ff09d9bcc52a8
[7/7] man/io_uring_enter.2: Fix typo "which is behaves" -> "which behaves"
      commit: 1ef00fc157cd0fa96d4da355ee86c977b6e4169e

Best regards,
-- 
Jens Axboe



           reply	other threads:[~2022-08-30 14:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <[email protected]>]

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=166186887874.35842.10405862161728511204.b4-ty@kernel.dk \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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