From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, 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, sachinp <sachinp@linux.vnet.ibm.com>,
Brian King <brking@linux.vnet.ibm.com>
Subject: Re: [PATCH net-next] net: fixup build after bpf header changes
Date: Tue, 4 Jan 2022 13:24:07 +0530 [thread overview]
Message-ID: <984e801f-494b-c84c-8efe-2d205af9bd7a@linux.vnet.ibm.com> (raw)
In-Reply-To: <20220104034827.1564167-1-kuba@kernel.org>
Hi
Thank You Jakub for the patch.
Kernel builds fine with given patch fix
Tested-by : Abdul haleem <abdhalee@linux.vnet.ibm.com>
On 1/4/22 9:18 AM, 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.
>
> Reported-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
> Fixes: e63a02348958 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next")
> Link: https://lore.kernel.org/all/7c03768d-d948-c935-a7ab-b1f963ac7eed@linux.vnet.ibm.com/
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: jesse.brandeburg@intel.com
> CC: anthony.l.nguyen@intel.com
> CC: saeedm@nvidia.com
> CC: leon@kernel.org
> CC: intel-wired-lan@lists.osuosl.org
> CC: linux-rdma@vger.kernel.org
> CC: bpf@vger.kernel.org
> ---
> drivers/net/ethernet/intel/ice/ice_nvm.c | 2 ++
> drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_nvm.c b/drivers/net/ethernet/intel/ice/ice_nvm.c
> index cd739a2c64e8..4eb0599714f4 100644
> --- a/drivers/net/ethernet/intel/ice/ice_nvm.c
> +++ b/drivers/net/ethernet/intel/ice/ice_nvm.c
> @@ -1,6 +1,8 @@
> // SPDX-License-Identifier: GPL-2.0
> /* Copyright (c) 2018, Intel Corporation. */
>
> +#include <linux/vmalloc.h>
> +
> #include "ice_common.h"
>
> /**
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> index efcf9d30b131..31c911182498 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> @@ -37,6 +37,7 @@
> #include <net/geneve.h>
> #include <linux/bpf.h>
> #include <linux/if_bridge.h>
> +#include <linux/filter.h>
> #include <net/page_pool.h>
> #include <net/xdp_sock_drv.h>
> #include "eswitch.h"
--
Regard's
Abdul Haleem
IBM Linux Technology Center
next prev parent reply other threads:[~2022-01-04 7:57 UTC|newest]
Thread overview: 5+ 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 7:24 ` Saeed Mahameed
2022-01-05 22:15 ` Saeed Mahameed
2022-01-04 7:54 ` Abdul Haleem [this message]
2022-01-04 12:40 ` 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=984e801f-494b-c84c-8efe-2d205af9bd7a@linux.vnet.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bpf@vger.kernel.org \
--cc=brking@linux.vnet.ibm.com \
--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=sachinp@linux.vnet.ibm.com \
--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 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 NNTP newsgroup(s).