From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>,
io-uring Mailing List <[email protected]>,
Pavel Begunkov <[email protected]>,
Stefan Metzmacher <[email protected]>,
Linux Kernel Mailing List <[email protected]>
Subject: Re: (subset) [PATCH v1 0/2] io_uring uapi updates
Date: Wed, 16 Nov 2022 13:34:57 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/16/22 6:14 AM, Jens Axboe wrote:
> On Wed, 16 Nov 2022 04:29:51 +0700, Ammar Faizi wrote:
>> From: Ammar Faizi <[email protected]>
>>
>> Hi Jens,
>>
>> io_uring uapi updates:
>>
>> 1) Don't force linux/time_types.h for userspace. Linux's io_uring.h is
>> synced 1:1 into liburing's io_uring.h. liburing has a configure
>> check to detect the need for linux/time_types.h (Stefan).
>>
>> [...]
>
> Applied, thanks!
>
> [1/2] io_uring: uapi: Don't force linux/time_types.h for userspace
> commit: 958bfdd734b6074ba88ee3abc69d0053e26b7b9c
Jens, please drop this commit. It breaks the build:
All errors (new ones prefixed by >>):
In file included from <command-line>:
>> ./usr/include/linux/io_uring.h:654:41: error: field 'timeout' has incomplete type
654 | struct __kernel_timespec timeout;
| ^~~~~~~
--
Ammar Faizi
next prev parent reply other threads:[~2022-11-16 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 21:29 [PATCH v1 0/2] io_uring uapi updates Ammar Faizi
2022-11-15 21:29 ` [PATCH v1 1/2] io_uring: uapi: Don't force linux/time_types.h for userspace Ammar Faizi
2022-11-15 21:29 ` [PATCH v1 2/2] io_uring: uapi: Don't use a zero-size array Ammar Faizi
2022-11-15 23:09 ` Jens Axboe
2022-11-16 10:14 ` Pavel Begunkov
2022-11-16 10:28 ` Ammar Faizi
2022-11-15 23:14 ` (subset) [PATCH v1 0/2] io_uring uapi updates Jens Axboe
2022-11-16 6:34 ` Ammar Faizi [this message]
2022-11-16 6:49 ` Ammar Faizi
2022-11-16 13:50 ` Jens Axboe
2022-11-16 14:22 ` Stefan Metzmacher
2022-11-16 19:46 ` Jens Axboe
2022-11-16 20:03 ` Stefan Metzmacher
2022-11-16 20:31 ` Pavel Begunkov
2022-11-16 20:18 ` Stefan Metzmacher
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