From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Daniel Xu <dxu@dxuuu.xyz>, Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: runtime warnings after merge of the bpf-next tree
Date: Thu, 1 Feb 2024 16:31:49 +1100 [thread overview]
Message-ID: <20240201163149.0d02fe46@canb.auug.org.au> (raw)
In-Reply-To: <CAADnVQJT8nOiiX90g3Pm7Ud0hzBBjBOQmPtPV1iwUYKMcuBFig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Hi all,
On Wed, 31 Jan 2024 20:02:28 -0800 Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
>
> On Wed, Jan 31, 2024 at 7:55 PM Daniel Xu <dxu@dxuuu.xyz> wrote:
> >
> > diff --git a/include/linux/btf_ids.h b/include/linux/btf_ids.h
> > index 0fe4f1cd1918..e24aabfe8ecc 100644
> > --- a/include/linux/btf_ids.h
> > +++ b/include/linux/btf_ids.h
> > @@ -227,7 +227,7 @@ BTF_SET8_END(name)
> > #define BTF_SET_END(name)
> > #define BTF_SET8_START(name) static struct btf_id_set8 __maybe_unused name = { 0 };
> > #define BTF_SET8_END(name)
> > -#define BTF_KFUNCS_START(name) static struct btf_id_set8 __maybe_unused name = { 0 };
> > +#define BTF_KFUNCS_START(name) static struct btf_id_set8 __maybe_unused name = { .flags = BTF_SET8_KFUNCS };
> > #define BTF_KFUNCS_END(name)
>
> Most likely you're correct.
> Force pushed bpf-next with this fix.
That fixed it for me, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-01 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:23 linux-next: runtime warnings after merge of the bpf-next tree Stephen Rothwell
2024-02-01 3:55 ` Alexei Starovoitov
2024-02-01 4:47 ` Stephen Rothwell
2024-02-01 3:55 ` Daniel Xu
2024-02-01 4:02 ` Alexei Starovoitov
2024-02-01 5:31 ` Stephen Rothwell [this message]
2024-02-01 4:53 ` Stephen Rothwell
2024-02-01 11:31 ` Marek Szyprowski
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=20240201163149.0d02fe46@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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