From: Mark Brown <broonie@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>,
Wireless <linux-wireless@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the wireless-next tree
Date: Wed, 22 Jul 2026 16:58:43 +0100 [thread overview]
Message-ID: <amDos20YUxH9DFgJ@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Hi all,
After merging the wireless-next tree, today's linux-next build
(arm64_defconfig.log /tmp/next/x86_64 allmodconfig) failed like this:
/tmp/next/build/net/mac80211/mlme.c:
In function 'ieee80211_rx_mgmt_assoc_resp':
/tmp/next/build/net/mac80211/mlme.c:7279:17: error: label 'abandon_assoc'
used but not defined
7279 | goto abandon_assoc;
| ^~~~
Caused by a semantic conflict (probably the same two patches as the
merge I posted a minute ago). I have applied the patch below and can
carry as needed:
diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
index 60fc407bb1ebb..5a1c022282202 100644
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -7276,7 +7276,7 @@ static void ieee80211_rx_mgmt_assoc_resp(struct ieee80211_sub_if_data *sdata,
else if (!assoc_data->s1g)
aid = le16_to_cpu(mgmt->u.assoc_resp.aid);
else if (status_code == WLAN_STATUS_SUCCESS)
- goto abandon_assoc;
+ goto notify_driver;
/*
* The 5 MSB of the AID field are reserved for a non-S1G STA. For
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-07-22 15:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 15:58 Mark Brown [this message]
2026-07-22 16:10 ` linux-next: build failure after merge of the wireless-next tree Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2025-01-16 2:08 Stephen Rothwell
2025-01-16 5:49 ` Ping-Ke Shih
2025-01-16 19:30 ` Kalle Valo
2024-10-09 1:04 Stephen Rothwell
2024-10-09 7:04 ` Johannes Berg
2014-09-08 8:42 Stephen Rothwell
2014-09-09 23:28 ` Stephen Rothwell
2014-09-09 23:37 ` David Miller
2014-09-10 17:46 ` John W. Linville
2014-07-16 3:28 Stephen Rothwell
2014-07-16 14:09 ` John W. Linville
2014-04-23 3:47 Stephen Rothwell
2014-04-23 20:54 ` Bing Zhao
2014-03-06 2:43 Stephen Rothwell
2014-03-06 8:53 ` Arend van Spriel
2014-03-06 2:24 Stephen Rothwell
2014-02-25 2:35 Stephen Rothwell
2014-02-25 19:07 ` John W. Linville
2014-02-25 20:47 ` Stephen Rothwell
2014-03-04 23:16 ` Stephen Rothwell
2014-03-04 23:21 ` Stephen Rothwell
2014-03-04 23:49 ` Greg KH
2014-02-13 2:19 Stephen Rothwell
2014-02-13 2:22 ` Stephen Rothwell
2014-02-13 17:31 ` Paul Gortmaker
2014-02-13 18:22 ` Paul Gortmaker
2014-02-13 18:28 ` Greg KH
2013-07-23 1:32 Stephen Rothwell
2013-07-23 7:24 ` Hauke Mehrtens
2013-04-02 2:34 Stephen Rothwell
2013-04-02 3:07 ` Larry Finger
2013-04-02 3:31 ` Stephen Rothwell
2013-04-02 4:07 ` Larry Finger
2012-04-12 2:24 Stephen Rothwell
2011-12-20 2:18 Stephen Rothwell
2011-12-20 2:42 ` Luis R. Rodriguez
2011-12-20 2:57 ` Stephen Rothwell
2011-12-20 3:24 ` Luis R. Rodriguez
2011-11-22 3:35 Stephen Rothwell
2011-11-22 8:03 ` Stanislaw Gruszka
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=amDos20YUxH9DFgJ@sirena.org.uk \
--to=broonie@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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