From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org,
Luciano Coelho <luciano.coelho@nokia.com>,
Luciano Coelho <coelho@ti.com>,
Juuso Oikarinen <juuso.oikarinen@nokia.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.15-rc4 (wireless/ti/wlcore)
Date: Wed, 07 May 2014 15:56:12 -0700 [thread overview]
Message-ID: <536ABA0C.7000907@infradead.org> (raw)
In-Reply-To: <1399377878-29995-1-git-send-email-geert@linux-m68k.org>
On 05/06/2014 05:04 AM, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.15-rc4[1] compared to v3.14[2].
>
>
>
> *** WARNINGS ***
>
> 181 regressions:
> + /scratch/kisskb/src/drivers/net/wireless/ti/wlcore/spi.c: warning: the frame size of 38080 bytes is larger than 1024 bytes [-Wframe-larger-than=]: => 317:1
Does that function: wl12xx_spi_raw_write() in spi.c actually work without crashing??
--
~Randy
parent reply other threads:[~2014-05-07 22:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1399377878-29995-1-git-send-email-geert@linux-m68k.org>]
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=536ABA0C.7000907@infradead.org \
--to=rdunlap@infradead.org \
--cc=coelho@ti.com \
--cc=geert@linux-m68k.org \
--cc=juuso.oikarinen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@nokia.com \
/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).