From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>
Subject: linux-next: build warning after merge of the mac80211 tree
Date: Fri, 29 Jan 2016 15:06:01 +1100 [thread overview]
Message-ID: <20160129150601.16f80af5@canb.auug.org.au> (raw)
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 :-(
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
next reply other threads:[~2016-01-29 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 4:06 Stephen Rothwell [this message]
2016-01-29 8:21 ` linux-next: build warning after merge of the mac80211 tree Johannes Berg
-- 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=20160129150601.16f80af5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).