From: Wan ZongShun <mcuos.com@gmail.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] Atmel/alsa: fix some code issues
Date: Mon, 7 Jun 2010 18:47:53 +0800 [thread overview]
Message-ID: <AANLkTikXHk_E8-F4OGsuAF6JFhgxjs3genWsY_ko2ohZ@mail.gmail.com> (raw)
In-Reply-To: <4C0CCCD6.9000809@atmel.com>
在 2010年6月7日 下午6:41,Nicolas Ferre <nicolas.ferre@atmel.com> 写道:
> Le 28/05/2010 04:27, Wan ZongShun :
>> Dear Nicolas,
>>
>> I am seeing the atmel codes as reference of my alsa driver programming.
>> Finding a few code issues, I make a patch to fix, thanks!
>
> After a brief review, I come back to this
>
>> Signed-off-by: Wan ZongShun<mcuos.com@gmail.com>
>>
>> ---
>> sound/soc/atmel/atmel-pcm.c | 2 +-
>> sound/soc/atmel/atmel_ssc_dai.c | 3 +--
>> 2 files changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/sound/soc/atmel/atmel-pcm.c b/sound/soc/atmel/atmel-pcm.c
>> index f6b3cc0..c69a8fb 100644
>> --- a/sound/soc/atmel/atmel-pcm.c
>> +++ b/sound/soc/atmel/atmel-pcm.c
>> @@ -478,7 +478,7 @@ struct snd_soc_platform atmel_soc_platform = {
>> .pcm_free = atmel_pcm_free_dma_buffers,
>> .suspend = atmel_pcm_suspend,
>> .resume = atmel_pcm_resume,
>> -};
>> +}
>
> Not ok for this. It is a structure declaration: we should keep the ";".
>
Okay, thanks!
>> EXPORT_SYMBOL_GPL(atmel_soc_platform);
>>
>> static int __init atmel_pcm_modinit(void)
>> diff --git a/sound/soc/atmel/atmel_ssc_dai.c b/sound/soc/atmel/atmel_ssc_dai.c
>> index 0b59806..4c44d13 100644
>> --- a/sound/soc/atmel/atmel_ssc_dai.c
>> +++ b/sound/soc/atmel/atmel_ssc_dai.c
>> @@ -549,7 +549,6 @@ static int atmel_ssc_hw_params(struct snd_pcm_substream
>> *substream,
>> printk(KERN_WARNING "atmel_ssc_dai: unsupported DAI format 0x%x\n",
>> ssc_p->daifmt);
>> return -EINVAL;
>> - break;
>
> Ok.
>
>> }
>> pr_debug("atmel_ssc_hw_params: "
>> "RCMR=%08x RFMR=%08x TCMR=%08x TFMR=%08x\n",
>> @@ -760,7 +759,7 @@ struct snd_soc_dai atmel_ssc_dai[NUM_SSC_DEVICES] = {
>> .private_data = &ssc_info[2],
>> },
>> #endif
>> -};
>> +}
>
> Not ok for this either. ditto.
>
>> EXPORT_SYMBOL_GPL(atmel_ssc_dai);
>>
>> static int __init atmel_ssc_modinit(void)
>
>
> --
> Nicolas Ferre
>
>
--
*linux-arm-kernel mailing list
mail addr:linux-arm-kernel@lists.infradead.org
you can subscribe by:
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
* linux-arm-NUC900 mailing list
mail addr:NUC900@googlegroups.com
main web: https://groups.google.com/group/NUC900
you can subscribe it by sending me mail:
mcuos.com@gmail.com
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next parent reply other threads:[~2010-06-07 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BFF2A19.1050002@gmail.com>
[not found] ` <4C0CCCD6.9000809@atmel.com>
2010-06-07 10:47 ` Wan ZongShun [this message]
2010-06-07 13:03 ` [PATCH] sound: atmel: trivial code cleanup Nicolas Ferre
2010-06-07 13:26 ` 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=AANLkTikXHk_E8-F4OGsuAF6JFhgxjs3genWsY_ko2ohZ@mail.gmail.com \
--to=mcuos.com@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=nicolas.ferre@atmel.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).