public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kalle Valo <kvalo@kernel.org>, Johannes Berg <johannes@sipsolutions.net>
Cc: Johannes Berg <johannes.berg@intel.com>,
	Wireless <linux-wireless@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Miri Korenblit <miriam.rachel.korenblit@intel.com>
Subject: linux-next: manual merge of the wireless-next tree with Linus' and the wireless trees
Date: Wed, 12 Mar 2025 13:53:06 +1100	[thread overview]
Message-ID: <20250312135306.2cd270b3@canb.auug.org.au> (raw)

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

Hi all,

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

  net/wireless/nl80211.c

between commits:

  1f860eb4cdda ("wifi: nl80211: disable multi-link reconfiguration")

from Linus' tree and

  2e85829ac7fb ("wifi: nl80211: fix assoc link handling")

from the wireless tree and commits:

  a096a8602f4f ("wifi: cfg80211: move link reconfig parameters into a struct")
  969241371f06 ("wifi: cfg80211: allow setting extended MLD capa/ops")

from the wireless-next tree.

I fixed it up (see below and I used the latter for the later hunk) 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 net/wireless/nl80211.c
index 34c0dfeeb7fc,aee49d43cf86..000000000000
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
@@@ -16512,10 -16518,7 +16524,10 @@@ static int nl80211_assoc_ml_reconf(stru
  
  	add_links = 0;
  	if (info->attrs[NL80211_ATTR_MLO_LINKS]) {
- 		err = nl80211_process_links(rdev, links,
 -		err = nl80211_process_links(rdev, req.add_links, NULL, 0, info);
++		err = nl80211_process_links(rdev, req.add_links,
 +					    /* mark as MLO, but not assoc */
 +					    IEEE80211_MLD_MAX_NUM_LINKS,
 +					    NULL, 0, info);
  		if (err)
  			return err;
  

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

             reply	other threads:[~2025-03-12  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  2:53 Stephen Rothwell [this message]
2025-03-12  8:11 ` linux-next: manual merge of the wireless-next tree with Linus' and the wireless trees Johannes Berg

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=20250312135306.2cd270b3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.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