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>
Subject: linux-next: build failure after merge of the wireless-next tree
Date: Wed, 9 Oct 2024 12:04:57 +1100 [thread overview]
Message-ID: <20241009120457.4bcebe8e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
Hi all,
After merging the wireless-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: modpost: "wireless_nlevent_flush" [net/wireless/cfg80211.ko] undefined!
Caused by commit
aee809aaa2d1 ("wifi: cfg80211: unexport wireless_nlevent_flush()")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-10-09 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 1:04 Stephen Rothwell [this message]
2024-10-09 7:04 ` 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
[not found] <20111220131802.e3782dfbf8172281a7df5a5c@canb.auug.org.au>
[not found] ` <CAB=NE6V12m2_u6YGxhmqjNGs9OjdOKFpCAYu5cs_Hezwwk9LLA@mail.gmail.com>
[not found] ` <20111220135704.8c87c166d9ac18d4ea308107@canb.auug.org.au>
2011-12-20 3:24 ` Luis R. Rodriguez
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=20241009120457.4bcebe8e@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 \
/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;
as well as URLs for NNTP newsgroup(s).