From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: bpf@vger.kernel.org
Subject: [PATCH bpf-next V2 0/2] bpf: avoid `attribute ignored' warnings in GCC
Date: Tue, 7 May 2024 09:42:25 +0200 [thread overview]
Message-ID: <20240507074227.4523-1-jose.marchesi@oracle.com> (raw)
These two patches avoid warnings (turned into errors) when building
the BPF selftests with GCC.
[Changes from V1:
- As requested by reviewer, an additional patch has been added in
order to remove __hidden from the `private' macro in
cpumask_common.h.
- Typo bening -> benign fixed in the commit message of the second
patch.]
Jose E. Marchesi (2):
bpf: avoid __hidden__ attribute in static object
bpf: disable some `attribute ignored' warnings in GCC
tools/testing/selftests/bpf/Makefile | 2 +-
tools/testing/selftests/bpf/progs/cpumask_common.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2024-05-07 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 7:42 Jose E. Marchesi [this message]
2024-05-07 7:42 ` [PATCH bpf-next V2 1/2] bpf: avoid __hidden__ attribute in static object Jose E. Marchesi
2024-05-07 7:42 ` [PATCH bpf-next V2 2/2] bpf: disable some `attribute ignored' warnings in GCC Jose E. Marchesi
2024-05-07 21:40 ` [PATCH bpf-next V2 0/2] bpf: avoid " 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=20240507074227.4523-1-jose.marchesi@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=bpf@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).