From: Mark Brown <broonie@opensource•wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Takashi Iwai <tiwai@suse•de>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: sound tree build warning
Date: Wed, 15 Jul 2009 09:35:21 +0100 [thread overview]
Message-ID: <20090715083521.GB8689@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20090715131354.da512c72.sfr@canb.auug.org.au>
On Wed, Jul 15, 2009 at 01:13:54PM +1000, Stephen Rothwell wrote:
> Today's linux-next build (x86_64 allmodconfig) produced this warning:
That's one of the configurations I regularly test build but I've not
seen this - which compiler are you using? Might be worth reporting that
along with warnings.
> sound/soc/codecs/wm8993.c: In function 'wm8993_hw_params':
> sound/soc/codecs/wm8993.c:1799: warning: array subscript is above array bounds
Fixed, though Takashi seems to be away at the minute so it'll not appear
in -next until he reappears.
next prev parent reply other threads:[~2009-07-15 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 3:13 linux-next: sound tree build warning Stephen Rothwell
2009-07-15 8:35 ` Mark Brown [this message]
2009-07-15 9:09 ` Takashi Iwai
2009-07-15 9:12 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2009-08-12 1:13 Stephen Rothwell
2009-08-12 5:58 ` Takashi Iwai
2009-08-12 13:33 ` Mark Brown
2009-08-11 3:22 Stephen Rothwell
2009-08-11 6:17 ` Takashi Iwai
2009-08-11 6:21 ` Stephen Rothwell
2009-08-10 4:15 Stephen Rothwell
2009-08-10 7:34 ` Takashi Iwai
2009-08-10 18:43 ` Mark Brown
2009-07-08 4:18 Stephen Rothwell
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=20090715083521.GB8689@rakim.wolfsonmicro.main \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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