From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Dylan Yudaken <dylany@fb.com>,
Pavel Begunkov <asml.silence@gmail.com>,
Facebook Kernel Team <kernel-team@fb.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Ammar Faizi <ammarfaizi2@gmail.com>
Subject: Re: [PATCH liburing 0/5] multishot recvmsg docs and example
Date: Tue, 26 Jul 2022 23:48:22 +0700 [thread overview]
Message-ID: <ce7096fb-0d42-99d7-e7fa-d82251c1934a@gnuweeb.org> (raw)
In-Reply-To: <d14c5be4-b9d8-a52c-12db-6f697784fd9e@kernel.dk>
On 7/26/22 11:40 PM, Jens Axboe wrote:
> On 7/26/22 10:32 AM, Ammar Faizi wrote:
>> On 7/26/22 11:23 PM, Jens Axboe wrote:
>>> [5/5] add an example for a UDP server
>>> commit: 61d472b51e761e61cbf46caea40aaf40d8ed1484
>>
>> This one breaks clang-13 build, I'll send a patch.
>
> Hmm, built fine with clang-13/14 here?
Not sure what is going on, but clang-13 on my machine is not happy:
io_uring-udp.c:134:18: error: incompatible pointer types passing \
'struct sockaddr_in6 *' to parameter of type 'const struct sockaddr *' \
[-Werror,-Wincompatible-pointer-types
io_uring-udp.c:142:18: error: incompatible pointer types passing \
'struct sockaddr_in *' to parameter of type 'const struct sockaddr *' \
[-Werror,-Wincompatible-pointer-types]
Changing the compiler to GCC builds just fine. I have fixed something like
this more than once. Strange indeed.
--
Ammar Faizi
next prev parent reply other threads:[~2022-07-26 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 12:14 [PATCH liburing 0/5] multishot recvmsg docs and example Dylan Yudaken
2022-07-26 12:14 ` [PATCH liburing 1/5] more consistent multishot recvmsg API parameter names Dylan Yudaken
2022-07-26 12:14 ` [PATCH liburing 2/5] order like functions together in liburing.h Dylan Yudaken
2022-07-26 12:15 ` [PATCH liburing 3/5] change io_uring_recvmsg_payload_length return type Dylan Yudaken
2022-07-26 12:15 ` [PATCH liburing 4/5] add documentation for multishot recvmsg Dylan Yudaken
2022-07-26 12:15 ` [PATCH liburing 5/5] add an example for a UDP server Dylan Yudaken
2022-07-26 16:23 ` [PATCH liburing 0/5] multishot recvmsg docs and example Jens Axboe
2022-07-26 16:32 ` Ammar Faizi
2022-07-26 16:40 ` Jens Axboe
2022-07-26 16:48 ` Ammar Faizi [this message]
2022-07-26 16:49 ` Jens Axboe
2022-07-27 7:57 ` Dylan Yudaken
2022-07-27 9:59 ` Ammar Faizi
2022-07-27 10:11 ` Ammar Faizi
2022-07-27 10:19 ` Ammar Faizi
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=ce7096fb-0d42-99d7-e7fa-d82251c1934a@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=ammarfaizi2@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=dylany@fb.com \
--cc=io-uring@vger.kernel.org \
--cc=kernel-team@fb.com \
/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 NNTP newsgroup(s).