From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: io-uring@vger.kernel.org
Subject: Re: (subset) [PATCH] io_uring: Avoid anonymous enums in io_uring uapi
Date: Thu, 28 Mar 2024 17:05:22 -0600 [thread overview]
Message-ID: <171166712200.796545.5071534678593541812.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240328210935.25640-1-krisman@suse.de>
On Thu, 28 Mar 2024 17:09:35 -0400, Gabriel Krisman Bertazi wrote:
> While valid C, anonymous enums confuse Cython (Python to C translator),
> as reported by Ritesh (YoSTEALTH) [1] . Since people rely on it when
> building against liburing and we want to keep this header in sync with
> the library version, let's name the existing enums in the uapi header.
>
> [1] https://github.com/cython/cython/issues/3240
>
> [...]
Applied, thanks!
[1/1] io_uring: Avoid anonymous enums in io_uring uapi
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-03-28 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 21:09 [PATCH] io_uring: Avoid anonymous enums in io_uring uapi Gabriel Krisman Bertazi
2024-03-28 23:05 ` Jens Axboe [this message]
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=171166712200.796545.5071534678593541812.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).