From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: linux-next: build warning after merge of the mac80211-next tree
Date: Fri, 11 May 2018 15:20:23 +0300 [thread overview]
Message-ID: <87po221j08.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20180509145624.643d2e56@canb.auug.org.au> (Stephen Rothwell's message of "Wed, 9 May 2018 14:56:24 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> After merging the mac80211-next tree, today's linux-next build (arm_multi
> v7_defconfig) produced this warning:
>
> drivers/net/wireless/marvell/mwifiex/uap_event.c: In function 'mwifiex_process_uap_event':
> drivers/net/wireless/marvell/mwifiex/uap_event.c:333:1: warning: the frame size of 1680 bytes is larger than 1024 bytes [-Wframe-larger-than=]
> }
> ^
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c: In function 'brcmf_notify_connect_status_ap':
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:5530:1: warning: the frame size of 1680 bytes is larger than 1024 bytes [-Wframe-larger-than=]
> }
> ^
>
> Maybe introduced by commit
>
> 52539ca89f36 ("cfg80211: Expose TXQ stats and parameters to userspace")
Btw Stephen for mac80211 reports it would be a good idea to also cc
linux-wireless list, in case Johannes is not around etc.
--
Kalle Valo
next prev parent reply other threads:[~2018-05-11 12:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 4:56 linux-next: build warning after merge of the mac80211-next tree Stephen Rothwell
2018-05-09 7:44 ` Johannes Berg
2018-05-11 12:20 ` Kalle Valo [this message]
2018-05-12 3:55 ` Stephen Rothwell
2018-05-12 3:55 ` Stephen Rothwell
2018-05-23 21:55 ` Arnd Bergmann
2018-05-23 21:55 ` Arnd Bergmann
2018-05-24 4:11 ` Kalle Valo
2018-05-24 8:51 ` Arnd Bergmann
2018-05-24 8:51 ` Arnd Bergmann
2018-05-24 10:08 ` Kalle Valo
2018-05-12 3:57 ` Stephen Rothwell
2020-11-09 5:43 Stephen Rothwell
2020-11-10 8:43 ` Johannes Berg
2021-04-13 10:33 Stephen Rothwell
2021-04-13 10:39 ` Grumbach, Emmanuel
2021-04-13 11:32 ` Johannes Berg
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=87po221j08.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=toke@toke.dk \
/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.