From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Kalle Valo <kvalo@kernel.org>
Cc: 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: Re: linux-next: build warning after merge of the wireless-next tree
Date: Fri, 09 Feb 2024 08:06:54 +0100 [thread overview]
Message-ID: <5a549dc1cc586e86206394519fe430236ff9de42.camel@sipsolutions.net> (raw)
In-Reply-To: <20240209142950.703eca9b@canb.auug.org.au>
On Fri, 2024-02-09 at 14:29 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the wireless-next tree, today's linux-next build (htmldocs)
> produced this warning:
>
> include/net/cfg80211.h:1067: warning: expecting prototype for cfg80211_chandef_primary_freq(). Prototype was for cfg80211_chandef_primary() instead
>
Strangely enough, I have a deja vu now, as if I'd fixed this before
somewhere. Oh well.
Thanks for the report, now fixed!
johannes
next prev parent reply other threads:[~2024-02-09 7:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 3:29 Stephen Rothwell
2024-02-09 7:06 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-14 2:49 Stephen Rothwell
2023-09-12 5:10 Stephen Rothwell
2023-03-23 3:15 Stephen Rothwell
2023-03-31 11:10 ` Kalle Valo
2023-02-15 4:20 Stephen Rothwell
2023-02-15 4:17 Stephen Rothwell
2023-01-19 5:24 Stephen Rothwell
2022-06-21 10:02 Stephen Rothwell
2022-05-17 10:00 Stephen Rothwell
2022-05-18 4:51 ` Kalle Valo
2014-09-30 8:46 Stephen Rothwell
2014-09-30 14:41 ` Larry Finger
2013-04-05 5:46 Stephen Rothwell
2013-04-04 1:00 Stephen Rothwell
2013-04-04 1:04 ` Stephen Rothwell
2013-04-04 1:17 ` Larry Finger
2013-04-04 2:36 ` Stephen Rothwell
2013-04-04 2:58 ` Larry Finger
2011-11-22 3:25 Stephen Rothwell
2011-11-22 7:56 ` 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=5a549dc1cc586e86206394519fe430236ff9de42.camel@sipsolutions.net \
--to=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=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®