From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Alviro Iskandar Setiawan <[email protected]>,
io-uring Mailing List <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH liburing v1 0/3] Fix Compilation Error on Android and Some Cleanup
Date: Thu, 20 Feb 2025 07:51:32 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 20 Feb 2025 21:34:19 +0700, Ammar Faizi wrote:
> Another day in the thrilling world of cross-platform compatibility...
>
> Alviro discovered that some Android versions are missing `aligned_alloc()`
> in `<stdlib.h>`, leading to a compilation error on Termux 0.118.0:
>
> ```
> cmd-discard.c:383:11: warning: call to undeclared library function \
> 'aligned_alloc' with type 'void *(unsigned long, unsigned long)'; ISO \
> C99 and later do not support implicit function declarations \
> [-Wimplicit-function-declaration]
>
> [...]
Applied, thanks!
[1/3] liburing.h: Remove redundant double negation
commit: 1d11475301931478bb35f2573e1741f5d9088132
[2/3] liburing.h: Explain the history of `io_uring_get_sqe()`
commit: d1c100351ffb3483f5d3fc661b2d41d48062bec1
[3/3] Fix missing `aligned_alloc()` on some Android devices
commit: 5c788d514b9ed6d1a3624150de8aa6db403c1c65
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-02-20 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 14:34 [PATCH liburing v1 0/3] Fix Compilation Error on Android and Some Cleanup Ammar Faizi
2025-02-20 14:34 ` [PATCH liburing v1 1/3] liburing.h: Remove redundant double negation Ammar Faizi
2025-02-20 14:34 ` [PATCH liburing v1 2/3] liburing.h: Explain the history of `io_uring_get_sqe()` Ammar Faizi
2025-02-20 14:34 ` [PATCH liburing v1 3/3] Fix missing `aligned_alloc()` on some Android devices Ammar Faizi
2025-02-20 14:51 ` 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=174006309264.1672035.6610273505554694557.b4-ty@kernel.dk \
[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