From: Kalle Valo <kvalo@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"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>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the mac80211-next tree
Date: Thu, 24 May 2018 13:08:38 +0300 [thread overview]
Message-ID: <87efi1cqmx.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAK8P3a3MMjg5oDVM_OAZ_nKeJ4zKK5PrDE+6UgQQfNxwEhRbMA@mail.gmail.com> (Arnd Bergmann's message of "Thu, 24 May 2018 10:51:17 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Thu, May 24, 2018 at 6:11 AM, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Arnd Bergmann <arnd@arndb.de> writes:
>>> I also bisected this new warning to the same commit above:
>>>
>>> net/batman-adv/bat_v_elp.c: In function 'batadv_v_elp_get_throughput':
>>> net/batman-adv/bat_v_elp.c:154:1: warning: the frame size of 1736
>>> bytes is larger than 1024 bytes [-Wframe-larger-than=]
>>
>> This should fix it:
>>
>> 8689c051a201 cfg80211: dynamically allocate per-tid stats for station info
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git/commit/?id=8689c051a20195b228e19acb155c7d6e48a86753
>
> Thanks for the pointer, I'll just wait for that to make it into
> linux-next (which hasn't been released in a few days now) then.
Yeah, Stephen announced that he won't be making linux-next builds this
week. I think he will be back next week.
--
Kalle Valo
next prev parent reply other threads:[~2018-05-24 10:08 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
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 [this message]
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=87efi1cqmx.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arnd@arndb.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@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.