All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: [wl-testing/master] build regression in brcmfmac
Date: Wed, 9 May 2018 23:12:41 +0200	[thread overview]
Message-ID: <5AF36449.9050906@broadcom.com> (raw)

Since yesterday I get the following build error on wl-testing/master:

   CC [M]  drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.o
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: 
error: the frame size of 1592 bytes is larger than 1024 bytes 
[-Werror=frame-larger-than=]
  }
  ^

In the function brcmf_notify_connect_status_ap() I do have following on 
the stack:

static s32
brcmf_notify_connect_status_ap(struct brcmf_cfg80211_info *cfg,
                                struct net_device *ndev,
                                const struct brcmf_event_msg *e, void *data)
{
         static int generation;
         u32 event = e->event_code;
         u32 reason = e->reason;
         struct station_info sinfo;

I guess the struct station_info grew bigger by these commits:

52539ca cfg80211: Expose TXQ stats and parameters to userspace	+816
81d5439 cfg80211: average ack rssi support for data frames	+1

There are a number of other (cfg80211-based) drivers doing the same 
thing, ie. mwifiex, ath6kl, qtnfmac.

Regards,
Arend

             reply	other threads:[~2018-05-09 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 21:12 Arend van Spriel [this message]
2018-05-09 21:22 ` [wl-testing/master] build regression in brcmfmac Johannes Berg
2018-05-09 21:27   ` Toke Høiland-Jørgensen
2018-05-09 21:30     ` Johannes Berg
2018-05-09 21:36       ` Toke Høiland-Jørgensen
2018-05-09 21:37         ` 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=5AF36449.9050906@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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 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.