From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, Johannes Berg <johannes@sipsolutions.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Xinming Hu <huxm@marvell.com>,
Amitkumar Karwar <akarwar@marvell.com>,
Avraham Stern <avraham.stern@intel.com>,
David Spinadel <david.spinadel@intel.com>,
Assaf Krauss <assaf.krauss@intel.com>,
Luca Coelho <luciano.coelho@intel.com>
Subject: Re: linux-next: build warning after merge of the wireless-drivers-next tree
Date: Fri, 8 Jul 2016 11:35:09 +1000 [thread overview]
Message-ID: <20160708113509.49c3c62a@canb.auug.org.au> (raw)
In-Reply-To: <20160708113214.7f371cb3@canb.auug.org.au>
Hi all,
On Fri, 8 Jul 2016 11:32:14 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the wireless-drivers-next tree, today's linux-next build
> (arm multi_v7_defconfig, x86_64 allmodconfig) produced this warning:
>
> drivers/net/wireless/marvell/mwifiex/scan.c: In function 'mwifiex_cancel_scan':
> drivers/net/wireless/marvell/mwifiex/scan.c:2031:44: warning: passing argument 2 of 'cfg80211_scan_done' makes pointer from integer without a cast [-Wint-conversion]
> cfg80211_scan_done(priv->scan_request, 1);
> ^
> In file included from include/net/mac80211.h:23:0,
> from drivers/net/wireless/marvell/mwifiex/decl.h:30,
> from drivers/net/wireless/marvell/mwifiex/scan.c:20:
> include/net/cfg80211.h:4104:6: note: expected 'struct cfg80211_scan_info *' but argument is of type 'int'
> void cfg80211_scan_done(struct cfg80211_scan_request *request,
> ^
>
> Introduced by commit
>
> a9c790ba23eb ("mwifiex: factor out mwifiex_cancel_scan")
>
> interacting with commit
>
> 1d76250bd34a ("nl80211: support beacon report scanning")
>
> from the net-next (and mac80211-next) tree.
>
> This will need some merge fix patch ... please send me or Dave one.
Of course, this is the conflict I reported against the mac80211-next
tree yesterday (the memory fades :-)) ... I will move the merge fix
patch from that tree to this one.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-07-08 1:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 1:32 linux-next: build warning after merge of the wireless-drivers-next tree Stephen Rothwell
2016-07-08 1:35 ` Stephen Rothwell [this message]
2016-07-20 2:25 Stephen Rothwell
2016-07-20 6:18 ` Reizer, Eyal
[not found] ` <8665E2433BC68541A24DFFCA87B70F5B3616184A-1tpBd5JUCm6IQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2016-07-20 18:41 ` Kalle Valo
2016-11-28 0:58 Stephen Rothwell
2016-11-28 7:25 ` Kalle Valo
2016-11-28 8:16 ` Barry Day
2016-11-28 11:44 ` Kalle Valo
2016-11-28 12:26 ` Jes Sorensen
2017-01-13 0:12 Stephen Rothwell
2017-01-13 13:47 ` Kalle Valo
2017-01-17 11:49 ` Kalle Valo
2019-01-30 23:46 Stephen Rothwell
2019-01-30 23:51 ` Luca Coelho
[not found] ` <9455f1b9e746f2c28d1573ccdce3836ece42cd8a.camel-XPOmlcxoEMv1KXRcyAk9cg@public.gmane.org>
2019-01-31 13:46 ` Kalle Valo
2019-01-31 20:52 ` Stephen Rothwell
2021-06-24 2:16 Stephen Rothwell
2021-06-24 5:49 ` Kalle Valo
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=20160708113509.49c3c62a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akarwar@marvell.com \
--cc=assaf.krauss@intel.com \
--cc=avraham.stern@intel.com \
--cc=davem@davemloft.net \
--cc=david.spinadel@intel.com \
--cc=huxm@marvell.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@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).