From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
saeedm@nvidia.com, leon@kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next] net: fixup build after bpf header changes
Date: Mon, 3 Jan 2022 23:24:11 -0800 [thread overview]
Message-ID: <20220104072411.esukmdx7sy3milmx@sx1> (raw)
In-Reply-To: <20220104034827.1564167-1-kuba@kernel.org>
On Mon, Jan 03, 2022 at 07:48:27PM -0800, Jakub Kicinski wrote:
>Recent bpf-next merge brought in header changes which uncovered
>includes missing in net-next which were not present in bpf-next.
>Build problems happen only on less-popular arches like hppa,
>sparc, alpha etc.
>
>I could repro the build problem with ice but not the mlx5 problem
>Abdul was reporting. mlx5 does look like it should include filter.h,
>anyway.
>
I got an internal report on the same thing also, but I couldn't repro
myself neither, I will ask them to test your patch.
WARNING: multiple messages have this Message-ID (diff)
From: Saeed Mahameed <saeed@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next] net: fixup build after bpf header changes
Date: Mon, 3 Jan 2022 23:24:11 -0800 [thread overview]
Message-ID: <20220104072411.esukmdx7sy3milmx@sx1> (raw)
In-Reply-To: <20220104034827.1564167-1-kuba@kernel.org>
On Mon, Jan 03, 2022 at 07:48:27PM -0800, Jakub Kicinski wrote:
>Recent bpf-next merge brought in header changes which uncovered
>includes missing in net-next which were not present in bpf-next.
>Build problems happen only on less-popular arches like hppa,
>sparc, alpha etc.
>
>I could repro the build problem with ice but not the mlx5 problem
>Abdul was reporting. mlx5 does look like it should include filter.h,
>anyway.
>
I got an internal report on the same thing also, but I couldn't repro
myself neither, I will ask them to test your patch.
next prev parent reply other threads:[~2022-01-04 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 3:48 [PATCH net-next] net: fixup build after bpf header changes Jakub Kicinski
2022-01-04 3:48 ` [Intel-wired-lan] " Jakub Kicinski
2022-01-04 7:24 ` Saeed Mahameed [this message]
2022-01-04 7:24 ` Saeed Mahameed
2022-01-05 22:15 ` Saeed Mahameed
2022-01-05 22:15 ` [Intel-wired-lan] " Saeed Mahameed
2022-01-04 7:54 ` Abdul Haleem
2022-01-04 7:54 ` [Intel-wired-lan] " Abdul Haleem
2022-01-04 12:40 ` patchwork-bot+netdevbpf
2022-01-04 12:40 ` [Intel-wired-lan] " 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=20220104072411.esukmdx7sy3milmx@sx1 \
--to=saeed@kernel.org \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.