All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Leon Romanovsky <leon@kernel.org>, David Miller <davem@davemloft.net>
Cc: Networking <netdev@vger.kernel.org>,
	Jianbo Liu <jianbol@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>
Subject: linux-next: manual merge of the mlx5-next tree with the net-next tree
Date: Thu, 2 Feb 2023 09:14:33 +1100	[thread overview]
Message-ID: <20230202091433.7fb9d936@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

Hi all,

Today's linux-next merge of the mlx5-next tree got a conflict in:

  include/linux/mlx5/driver.h

between commit:

  fe298bdf6f65 ("net/mlx5: Prepare for fast crypto key update if hardware supports it")

from the net-next tree and commit:

  2fd0e75727a8 ("net/mlx5e: Propagate an internal event in case uplink netdev changes")

from the mlx5-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/driver.h
index 234334194b38,cc48aa308269..000000000000
--- a/include/linux/mlx5/driver.h
+++ b/include/linux/mlx5/driver.h
@@@ -674,7 -675,7 +675,8 @@@ struct mlx5e_resources 
  	} hw_objs;
  	struct devlink_port dl_port;
  	struct net_device *uplink_netdev;
 +	struct mlx5_crypto_dek_priv *dek_priv;
+ 	struct mutex uplink_netdev_lock;
  };
  
  enum mlx5_sw_icm_type {

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-02-01 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 22:14 Stephen Rothwell [this message]
2023-02-02  8:26 ` linux-next: manual merge of the mlx5-next tree with the net-next tree Leon Romanovsky
  -- strict thread matches above, loose matches on Subject: below --
2023-10-02 23:37 Stephen Rothwell
2023-10-03 10:17 ` Leon Romanovsky
2023-08-15  2:28 Stephen Rothwell
2022-09-15  0:20 Stephen Rothwell
2022-09-15  0:15 Stephen Rothwell
2019-06-27  4:09 Stephen Rothwell
2019-06-27 22:59 ` Saeed Mahameed

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=20230202091433.7fb9d936@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=davem@davemloft.net \
    --cc=jianbol@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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.