public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Linux Kernel Mailing List <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Bart Van Assche <[email protected]>,
	Dylan Yudaken <[email protected]>,
	Facebook Kernel Team <[email protected]>,
	Kanna Scarlet <[email protected]>
Subject: [PATCH liburing 0/2] liburing uapi and manpage update
Date: Tue, 23 Aug 2022 18:52:42 +0700	[thread overview]
Message-ID: <[email protected]> (raw)

From: Ammar Faizi <[email protected]>

Hi Jens,

There are two patches in this series.

1) Sync the argument data type with `man 2 renameat`.

2) On top of io_uring series I just sent, copy uapi io_uring.h to
   liburing. Sync with the kernel.

Signed-off-by: Ammar Faizi <[email protected]>
---

Ammar Faizi (2):
  liburing: Change the type of `flags` in `io_uring_prep_renameat()` to `unsigned int`
  io_uring: uapi: Sync with the kernel

 man/io_uring_prep_renameat.3    |  4 +-
 src/include/liburing.h          |  2 +-
 src/include/liburing/io_uring.h | 66 ++++++++++++++++++++++++---------
 3 files changed, 51 insertions(+), 21 deletions(-)


base-commit: bf3fedba890e66d644692910964fe1d8cbf4fb1b
-- 
Ammar Faizi


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 11:52 Ammar Faizi [this message]
2022-08-23 11:52 ` [PATCH 1/2] liburing: Change the type of `flags` in `io_uring_prep_renameat()` to `unsigned int` Ammar Faizi
2022-08-23 11:52 ` [PATCH 2/2] io_uring: uapi: Sync with the kernel Ammar Faizi
2022-08-23 13:23 ` [PATCH liburing 0/2] liburing uapi and manpage update 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 \
    [email protected] \
    [email protected] \
    [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