From: garlic.tseng@mediatek.com (Garlic Tseng)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH -next v2] ASoC: mediatek: mt2701: fix non static symbol warning
Date: Mon, 11 Jul 2016 09:31:25 +0800 [thread overview]
Message-ID: <1468200685.32731.1.camel@mtksdaap41> (raw)
In-Reply-To: <1467985621-13755-1-git-send-email-weiyj_lk@163.com>
On Fri, 2016-07-08 at 13:47 +0000, weiyj_lk at 163.com wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> Fixes the following sparse warning:
>
> sound/soc/mediatek/mt2701/mt2701-afe-pcm.c:72:5: warning:
> symbol 'mt2701_dai_num_to_i2s' was not declared. Should it be static?
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Acked-by: Garlic Tseng <garlic.tseng@mediatek.com>
> ---
> sound/soc/mediatek/mt2701/mt2701-afe-pcm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/mediatek/mt2701/mt2701-afe-pcm.c b/sound/soc/mediatek/mt2701/mt2701-afe-pcm.c
> index 15522c0..34a6123 100644
> --- a/sound/soc/mediatek/mt2701/mt2701-afe-pcm.c
> +++ b/sound/soc/mediatek/mt2701/mt2701-afe-pcm.c
> @@ -69,7 +69,7 @@ static const struct mt2701_afe_rate mt2701_afe_i2s_rates[] = {
> { .rate = 352800, .regvalue = 24 },
> };
>
> -int mt2701_dai_num_to_i2s(struct mtk_base_afe *afe, int num)
> +static int mt2701_dai_num_to_i2s(struct mtk_base_afe *afe, int num)
> {
> int val = num - MT2701_IO_I2S;
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel at alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-07-11 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 13:41 [PATCH -next] ASoC: mediatek: mt2701: cHECK-fix non static symbol warning weiyj_lk at 163.com
2016-07-08 13:47 ` [PATCH -next v2] ASoC: mediatek: mt2701: fix " weiyj_lk at 163.com
2016-07-11 1:31 ` Garlic Tseng [this message]
2016-07-14 16:32 ` Applied "ASoC: mediatek: mt2701: fix non static symbol warning" to the asoc tree 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=1468200685.32731.1.camel@mtksdaap41 \
--to=garlic.tseng@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox