[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20240531124415.05b25e7a@canb.auug.org.au>
Date: Fri, 31 May 2024 12:44:15 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kalle Valo <kvalo@...nel.org>, Johannes Berg <johannes@...solutions.net>
Cc: Wireless <linux-wireless@...r.kernel.org>, Aditya Kumar Singh
<quic_adisi@...cinc.com>, Johannes Berg <johannes.berg@...el.com>, Linux
Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the wireless-next tree with the
wireless tree
Hi all,
Today's linux-next merge of the wireless-next tree got a conflict in:
net/mac80211/cfg.c
between commit:
8ecc4d7a7cd3 ("wifi: mac80211: pass proper link id for channel switch started notification")
from the wireless tree and commit:
344d18cec231 ("wifi: mac80211: collect some CSA data into sub-structs")
from the wireless-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 net/mac80211/cfg.c
index 83ad6c9709fe,62119e957cd8..000000000000
--- a/net/mac80211/cfg.c
+++ b/net/mac80211/cfg.c
@@@ -4028,7 -4028,7 +4029,7 @@@ __ieee80211_channel_switch(struct wiph
}
cfg80211_ch_switch_started_notify(sdata->dev,
- &link_data->csa_chanreq.oper, link_id,
- &link_data->csa.chanreq.oper, 0,
++ &link_data->csa.chanreq.oper, link_id,
params->count, params->block_tx);
if (changed) {
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists