From: Cupertino Miranda <cupertino.miranda@oracle.com>
To: bpf@vger.kernel.org
Cc: Cupertino Miranda <cupertino.miranda@oracle.com>,
jose.marchesi@oracle.com, david.faust@oracle.com,
Yonghong Song <yonghong.song@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: [PATCH bpf-next n2 0/1] selftests/bpf: Fix a few tests for GCC related
Date: Fri, 10 May 2024 19:38:49 +0100 [thread overview]
Message-ID: <20240510183850.286661-1-cupertino.miranda@oracle.com> (raw)
Hi everyone,
This is version 2 for the proposed patch.
In initial version I rather disabled the warnings from showing for the
particular tests, as I was afraid I would change the test purpose by
changing the code.
This time I corrected the warnings in GCC by adapting the code.
For jeq_infer_not_null_fail.c, it seems rather more intricate to fix the
warning. In this particular case I left the disabled warning. If you
rather think that it can be fixed I hope you can advise me how to.
Best regards,
Cupertino
Changes from v1:
- Fixes warnings by actual code changes.
Cc: jose.marchesi@oracle.com
Cc: david.faust@oracle.com
Cc: Yonghong Song <yonghong.song@linux.dev>
Cc: Eduard Zingerman <eddyz87@gmail.com>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cupertino Miranda (1):
selftests/bpf: Fix a few tests for GCC related warnings.
.../selftests/bpf/progs/cpumask_failure.c | 3 --
.../testing/selftests/bpf/progs/dynptr_fail.c | 12 ++---
.../bpf/progs/jeq_infer_not_null_fail.c | 4 ++
.../selftests/bpf/progs/test_tunnel_kern.c | 47 +++++++++++--------
4 files changed, 37 insertions(+), 29 deletions(-)
--
2.39.2
next reply other threads:[~2024-05-10 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 18:38 Cupertino Miranda [this message]
2024-05-10 18:38 ` [PATCH bpf-next v2 1/1] selftests/bpf: Fix a few tests for GCC related warnings Cupertino Miranda
2024-05-13 0:30 ` [PATCH bpf-next n2 0/1] selftests/bpf: Fix a few tests for GCC related patchwork-bot+netdevbpf
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=20240510183850.286661-1-cupertino.miranda@oracle.com \
--to=cupertino.miranda@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.com \
--cc=yonghong.song@linux.dev \
/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).