From: Ammar Faizi <[email protected]>
To: Dylan Yudaken <[email protected]>, Jens Axboe <[email protected]>
Cc: Facebook Kernel Team <[email protected]>,
Pavel Begunkov <[email protected]>,
Bart Van Assche <[email protected]>,
io-uring Mailing List <[email protected]>
Subject: Re: [PATCH liburing 2/4] add IORING_RECV_MULTISHOT to io_uring.h
Date: Tue, 28 Jun 2022 23:10:01 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/28/22 10:04 PM, Dylan Yudaken wrote:
> copy from include/uapi/linux/io_uring.h
>
> Signed-off-by: Dylan Yudaken <[email protected]>
> ---
> src/include/liburing/io_uring.h | 53 ++++++++++++++++++++++++---------
> 1 file changed, 39 insertions(+), 14 deletions(-)
>
> diff --git a/src/include/liburing/io_uring.h b/src/include/liburing/io_uring.h
> index 2f391c9..1e5bdb3 100644
> --- a/src/include/liburing/io_uring.h
> +++ b/src/include/liburing/io_uring.h
> @@ -10,10 +10,7 @@
>
> #include <linux/fs.h>
> #include <linux/types.h>
> -
> -#ifdef __cplusplus
> -extern "C" {
> -#endif
Dylan,
That `extern "C"` thing is for C++, we shouldn't omit it.
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?
Just for reference, that line is introduced in commit:
commit 3d74c677c45eccf36b92f7ad4b3317adc1ed06bb
Author: Bart Van Assche <[email protected]>
Date: Sun Jun 28 12:58:19 2020 -0700
Make the liburing header files again compatible with C++
Include <atomic> instead of <stdatomic.h> if built with a C++ compiler.
Fixes: b9c0bf79aa87 ("src/include/liburing/barrier.h: Use C11 atomics")
Signed-off-by: Bart Van Assche <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
src/include/liburing.h | 8 ++++----
src/include/liburing/barrier.h | 37 +++++++++++++++++++++++++++++++++++--
src/include/liburing/io_uring.h | 8 ++++++++
3 files changed, 47 insertions(+), 6 deletions(-)
Adding the author to the CC list.
--
Ammar Faizi
next prev parent reply other threads:[~2022-06-28 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 15:04 [PATCH liburing 0/4] liburing: multishot receive Dylan Yudaken
2022-06-28 15:04 ` [PATCH liburing 1/4] add t_create_socket_pair Dylan Yudaken
2022-06-28 15:04 ` [PATCH liburing 2/4] add IORING_RECV_MULTISHOT to io_uring.h Dylan Yudaken
2022-06-28 16:10 ` Ammar Faizi [this message]
2022-06-28 16:12 ` Jens Axboe
2022-06-28 16:12 ` Dylan Yudaken
2022-06-28 16:12 ` Dylan Yudaken
2022-06-28 15:04 ` [PATCH liburing 3/4] add recv-multishot test Dylan Yudaken
2022-06-28 15:04 ` [PATCH liburing 4/4] add IORING_RECV_MULTISHOT docs Dylan Yudaken
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] \
/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