[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20211020103414.3e7533f4@canb.auug.org.au>
Date: Wed, 20 Oct 2021 10:34:14 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>,
Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>
Cc: Aharon Landau <aharonl@...dia.com>,
Leon Romanovsky <leon@...nel.org>,
Leon Romanovsky <leonro@...dia.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Maor Gottlieb <maorg@...dia.com>,
Mark Zhang <markzhang@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>
Subject: linux-next: manual merge of the net-next tree with the rdma tree
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
include/linux/mlx5/fs.h
between commit:
b8dfed636fc6 ("net/mlx5: Add priorities for counters in RDMA namespaces")
from the rdma tree and commit:
425a563acb1d ("net/mlx5: Introduce port selection namespace")
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 include/linux/mlx5/fs.h
index f2c3da2006d9,7a43fec63a35..000000000000
--- a/include/linux/mlx5/fs.h
+++ b/include/linux/mlx5/fs.h
@@@ -83,8 -83,7 +83,9 @@@ enum mlx5_flow_namespace_type
MLX5_FLOW_NAMESPACE_RDMA_RX,
MLX5_FLOW_NAMESPACE_RDMA_RX_KERNEL,
MLX5_FLOW_NAMESPACE_RDMA_TX,
+ MLX5_FLOW_NAMESPACE_RDMA_RX_COUNTERS,
+ MLX5_FLOW_NAMESPACE_RDMA_TX_COUNTERS,
+ MLX5_FLOW_NAMESPACE_PORT_SEL,
};
enum {
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists