From: Lee Jones <lee.jones@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Wei Yongjun <weiyj.lk@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"perex@perex.cz" <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Fabio Baltieri <fabio.baltieri@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] ASoC: ux500: Fix sparse non static symbol warning
Date: Wed, 8 Jan 2014 11:06:03 +0000 [thread overview]
Message-ID: <20140108110603.GG19974@lee--X1> (raw)
In-Reply-To: <CACRpkdYet_yzg0jhd4DiEyTMjL42FAb9DsYPWRv=AXVbz1Tvuw@mail.gmail.com>
On Wed, 08 Jan 2014, Linus Walleij wrote:
> On Wed, Jan 8, 2014 at 11:13 AM, Wei Yongjun <weiyj.lk@gmail.com> wrote:
> > From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> >
> > Fixes the following sparse warning:
> >
> > sound/soc/ux500/ux500_msp_i2s.c:649:5: warning:
> > symbol 'ux500_msp_i2s_of_init_msp' was not declared. Should it be static?
> >
> > Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
FWIW: Acked-by: Lee Jones <lee.jones@linaro.org>
> Lee, is this something that needs to go along with your patches to
> ASoC or can I apply this separately?
If Mark takes it, then it will just apply as my patches have already
been applied.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-01-08 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 10:13 [PATCH -next] ASoC: ux500: Fix sparse non static symbol warning Wei Yongjun
2014-01-08 10:14 ` Arnd Bergmann
2014-01-08 10:17 ` Linus Walleij
2014-01-08 11:06 ` Lee Jones [this message]
2014-01-08 11:58 ` Linus Walleij
2014-01-08 12:22 ` Mark Brown
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=20140108110603.GG19974@lee--X1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=fabio.baltieri@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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