From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ammar Faizi <ammarfaizi2@gnuweeb.org>
Subject: [PATCH liburing v1 2/3] github: Append `-Wno-sign-compare` to the GitHub build bot CFLAGS
Date: Wed, 8 Mar 2023 03:38:29 +0700 [thread overview]
Message-ID: <20230307203830.612939-3-ammarfaizi2@gnuweeb.org> (raw)
In-Reply-To: <20230307203830.612939-1-ammarfaizi2@gnuweeb.org>
Kill the sign-compare warning on the GitHub build bot because Jens
doesn't like it. See commit 4c79857b9354 ("examples/send-zerocopy:
cleanups").
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
.github/workflows/build.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 29b80bfec1d208c0..fed5b38c3a507336 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -86,7 +86,7 @@ jobs:
cxx: mips-linux-gnu-g++
env:
- FLAGS: -g -O3 -Wall -Wextra -Werror ${{matrix.extra_flags}}
+ FLAGS: -g -O3 -Wall -Wextra -Werror -Wno-sign-compare ${{matrix.extra_flags}}
# Flags for building sources in src/ dir only.
LIBURING_CFLAGS: ${{matrix.liburing_extra_flags}}
--
Ammar Faizi
next prev parent reply other threads:[~2023-03-07 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 20:38 [PATCH liburing v1 0/3] Small fixes and CI update Ammar Faizi
2023-03-07 20:38 ` [PATCH liburing v1 1/3] io_uring-udp: Fix the wrong `inet_ntop()` argument Ammar Faizi
2023-03-07 20:38 ` Ammar Faizi [this message]
2023-03-07 20:38 ` [PATCH liburing v1 3/3] man/io_uring_register_{buffers,files}: Kill trailing whitespaces Ammar Faizi
2023-03-07 20:55 ` [PATCH liburing v1 0/3] Small fixes and CI update Jens Axboe
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=20230307203830.612939-3-ammarfaizi2@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®