From: Yonghong Song <yhs@meta.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: patchwork-bot+netdevbpf@kernel.org,
Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
netdev@vger.kernel.org, kuba@kernel.org, kernel-team@fb.com,
gustavoars@kernel.org
Subject: Re: [PATCH bpf 1/2] net/ipv4: fix linux/in.h header dependencies
Date: Mon, 7 Nov 2022 17:08:05 -0800 [thread overview]
Message-ID: <97333915-9a71-1c6d-aae5-5813e1828f84@meta.com> (raw)
In-Reply-To: <CAEf4BzbuaTk1KdYJ5w_8wQLo01i_+js-jvYbTZ_zeWwGm9Zu=A@mail.gmail.com>
On 11/7/22 4:56 PM, Andrii Nakryiko wrote:
> On Thu, Nov 3, 2022 at 9:18 AM Yonghong Song <yhs@meta.com> wrote:
>>
>>
>>
>> On 11/3/22 5:50 AM, patchwork-bot+netdevbpf@kernel.org wrote:
>>> Hello:
>>>
>>> This series was applied to bpf/bpf.git (master)
>>> by Daniel Borkmann <daniel@iogearbox.net>:
>>>
>>> On Wed, 2 Nov 2022 11:25:16 -0700 you wrote:
>>>> __DECLARE_FLEX_ARRAY is defined in include/uapi/linux/stddef.h but
>>>> doesn't seem to be explicitly included from include/uapi/linux/in.h,
>>>> which breaks BPF selftests builds (once we sync linux/stddef.h into
>>>> tools/include directory in the next patch). Fix this by explicitly
>>>> including linux/stddef.h.
>>>>
>>>> Given this affects BPF CI and bpf tree, targeting this for bpf tree.
>>>>
>>>> [...]
>>>
>>> Here is the summary with links:
>>> - [bpf,1/2] net/ipv4: fix linux/in.h header dependencies
>>> https://git.kernel.org/bpf/bpf/c/aec1dc972d27
>>> - [bpf,2/2] tools headers uapi: pull in stddef.h to fix BPF selftests build in CI
>>> https://git.kernel.org/bpf/bpf/c/a778f5d46b62
>>
>> Can we put this patch set into bpf-next as well? Apparently we have the
>> same issue in bpf-next.
>>
>
> Unfortunately we can't because they are already in bpf, and if we have
> them in bpf-next, they will cause merge conflicts. So I currently
> cherry-pick those two patches locally when compiling selftests. This
> should hopefully will be fixed soon and bpf and bpf-next will
> converge.
Thanks. This should be fine. I guess most people will do the same
thing (cherry-pick locally).
>
>>>
>>> You are awesome, thank you!
prev parent reply other threads:[~2022-11-08 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 18:25 [PATCH bpf 1/2] net/ipv4: fix linux/in.h header dependencies Andrii Nakryiko
2022-11-02 18:25 ` [PATCH bpf 2/2] tools headers uapi: pull in stddef.h to fix BPF selftests build in CI Andrii Nakryiko
2022-11-03 12:50 ` [PATCH bpf 1/2] net/ipv4: fix linux/in.h header dependencies patchwork-bot+netdevbpf
2022-11-03 16:17 ` Yonghong Song
2022-11-08 0:56 ` Andrii Nakryiko
2022-11-08 1:08 ` Yonghong Song [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=97333915-9a71-1c6d-aae5-5813e1828f84@meta.com \
--to=yhs@meta.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gustavoars@kernel.org \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@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