[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20210324122137.5ff8f0b2@canb.auug.org.au>
Date: Wed, 24 Mar 2021 12:21:37 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Parav Pandit <parav@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>,
Wan Jiabing <wanjiabing@...o.com>
Subject: linux-next: manual merge of the net-next tree with the net tree
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/sf/hw_table.c
between commit:
7c1ef1959b6f ("net/mlx5: SF, do not use ecpu bit for vhca state processing")
from the net tree and commit:
4c94fe88cde4 ("net: ethernet: Remove duplicate include of vhca_event.h")
from the net-next tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc drivers/net/ethernet/mellanox/mlx5/core/sf/hw_table.c
index a5a0f60bef66,3c8a00dd573a..000000000000
--- a/drivers/net/ethernet/mellanox/mlx5/core/sf/hw_table.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/sf/hw_table.c
@@@ -5,8 -5,7 +5,7 @@@
#include "priv.h"
#include "sf.h"
#include "mlx5_ifc_vhca_event.h"
- #include "vhca_event.h"
-#include "ecpf.h"
+#include "mlx5_core.h"
struct mlx5_sf_hw {
u32 usr_sfnum;
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists