From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH liburing] test/helpers: Use a proper cast for `(struct sockaddr *)` argument
Date: Sun, 03 Jul 2022 07:00:20 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Sun, 3 Jul 2022 13:44:05 +0700, Ammar Faizi wrote:
> From: Ammar Faizi <[email protected]>
>
> Sometimes the compiler accepts (struct sockaddr_in *) to be passed in
> to (struct sockaddr *) without a cast. But not all compilers agree with
> that. Building with clang 13.0.1 yields the following error:
>
> error: incompatible pointer types passing 'struct sockaddr_in *' to \
> parameter of type 'struct sockaddr *' [-Werror,-Wincompatible-pointer-types]
>
> [...]
Applied, thanks!
[1/1] test/helpers: Use a proper cast for `(struct sockaddr *)` argument
commit: 752c325dcde43be8d87f83b16d346beac5e1de2a
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-07-03 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 6:44 [PATCH liburing] test/helpers: Use a proper cast for `(struct sockaddr *)` argument Ammar Faizi
2022-07-03 13:00 ` 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=165685322035.1103909.10554403221181770675.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