From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the mac80211 tree
Date: Fri, 29 Jan 2016 09:21:15 +0100 [thread overview]
Message-ID: <1454055675.3369.0.camel@sipsolutions.net> (raw)
In-Reply-To: <20160129150601.16f80af5@canb.auug.org.au>
On Fri, 2016-01-29 at 15:06 +1100, Stephen Rothwell wrote:
> Hi Johannes,
>
> After merging the mac80211 tree, today's linux-next build (i386
> defconfig)
> produced this warning:
>
> In file included from include/net/wext.h:4:0,
> from net/socket.c:97:
> include/net/iw_handler.h:446:13: warning: 'wireless_nlevent_flush'
> defined but not used [-Wunused-function]
> static void wireless_nlevent_flush(void) {}
> ^
>
> Introduced by commit
>
> 3730abeab65b ("cfg80211/wext: fix message ordering")
>
> Missing inline :-(
Oops. Fixed, thanks.
johannes
next prev parent reply other threads:[~2016-01-29 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 4:06 linux-next: build warning after merge of the mac80211 tree Stephen Rothwell
2016-01-29 8:21 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-29 7:30 Stephen Rothwell
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=1454055675.3369.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.