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 0/2] Maintainer and uapi header update
Date: Tue, 23 Aug 2022 18:45:47 +0700	[thread overview]
Message-ID: <[email protected]> (raw)

From: Ammar Faizi <[email protected]>

Hi Jens,

There are two patches in this series.

1) MAINTAINERS: Add `include/linux/io_uring_types.h`.

File include/linux/io_uring_types.h doesn't have a maintainer, add it
to the io_uring section.

2) io_uring: uapi: Add `extern "C"` in io_uring.h for liburing.

On Tue, 28 Jun 2022 10:12:27 -0600, Jens Axboe wrote:
> On 6/28/22 10:10 AM, Ammar Faizi wrote:
>> Or better add that to the kernel tree as well, it won't break
>> the kernel because we have a __cplusplus guard here.
>> 
>> Jens what do you think?
>
> It'd be nice to keep them fully in sync. If I recall correctly, the only
> differences right now is that clause, and the change to not using a zero
> sized array at the end of a struct (which is slated for the kernel too).

^ Do that.

Ref: https://lore.kernel.org/io-uring/[email protected]

Make it easy for liburing to integrate uapi header with the kernel.
Previously, when this header changes, the liburing side can't directly
copy this header file due to some small differences. Sync them.

Cc: Bart Van Assche <[email protected]>
Cc: Dylan Yudaken <[email protected]>
Cc: Facebook Kernel Team <[email protected]>
Signed-off-by: Ammar Faizi <[email protected]>
---

Ammar Faizi (2):
  MAINTAINERS: Add `include/linux/io_uring_types.h`
  io_uring: uapi: Add `extern "C"` in io_uring.h for liburing

 MAINTAINERS                   | 1 +
 include/uapi/linux/io_uring.h | 8 ++++++++
 2 files changed, 9 insertions(+)


base-commit: 3f743e9bbb8fe20f4c477e4bf6341c4187a4a264
-- 
Ammar Faizi


             reply	other threads:[~2022-08-23 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 11:45 Ammar Faizi [this message]
2022-08-23 11:45 ` [PATCH 1/2] MAINTAINERS: Add `include/linux/io_uring_types.h` Ammar Faizi
2022-08-23 11:45 ` [PATCH 2/2] io_uring: uapi: Add `extern "C"` in io_uring.h for liburing Ammar Faizi
2022-08-23 13:23 ` [PATCH 0/2] Maintainer and uapi header 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