From: Marek Belisko <marek.belisko@streamunlimited.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 2/2] ASoC: pcm1681: Improve the logic for de-emphasis sampling rate selection
Date: Fri, 24 Jul 2015 14:07:48 +0200 [thread overview]
Message-ID: <55B22A94.7000802@streamunlimited.com> (raw)
In-Reply-To: <CAFRkauBWWm9j0ZjqxU50hTkiaA24+6RfAFSELSys2k6=tmpNTg@mail.gmail.com>
On 07/24/2015 07:48 AM, Axel Lin wrote:
> 2015-07-24 13:22 GMT+08:00 Marek Belisko <marek.belisko@streamunlimited.com>:
>> On 07/24/2015 03:17 AM, Axel Lin wrote:
>>> 2015-07-24 3:48 GMT+08:00 Marek Belisko <marek.belisko@streamunlimited.com>:
>>>> Hi Axel,
>>>>
>>>> On 23.07.2015 17:23, Axel Lin wrote:
>>>>>
>>>>> Slightly improve the logic for de-emphasis sampling rate selection by
>>>>> break
>>>>> out the loop if the rate is matched.
>>>>>
>>>>> Signed-off-by: Axel Lin <axel.lin@ingics.com>
>>>>> ---
>>>>> sound/soc/codecs/pcm1681.c | 13 +++++++++----
>>>>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>>>>
>>>>> diff --git a/sound/soc/codecs/pcm1681.c b/sound/soc/codecs/pcm1681.c
>>>>> index 1011142..5832523 100644
>>>>> --- a/sound/soc/codecs/pcm1681.c
>>>>> +++ b/sound/soc/codecs/pcm1681.c
>>>>> @@ -95,17 +95,22 @@ static int pcm1681_set_deemph(struct snd_soc_codec
>>>>> *codec)
>>>>> struct pcm1681_private *priv = snd_soc_codec_get_drvdata(codec);
>>>>> int i = 0, val = -1, enable = 0;
>>>>>
>>>>> - if (priv->deemph)
>>>>> - for (i = 0; i < ARRAY_SIZE(pcm1681_deemph); i++)
>>>>> - if (pcm1681_deemph[i] == priv->rate)
>>>>> + if (priv->deemph) {
>>>>> + for (i = 0; i < ARRAY_SIZE(pcm1681_deemph); i++) {
>>>>> + if (pcm1681_deemph[i] == priv->rate) {
>>>>> val = i;
>>>>> + break;
>>>>> + }
>>>>> + }
>>>>> + }
>>>>
>>>> ^^^^^^^
>>>> I think we don't need those brackets only for if statement (where you add
>>>> break)
>>>
>>> Because I think having the brackets here makes the code looks better.
>> If we follow CodingStyle then it says no brackets around single statement.
>
> Yes, but it's not always good if the "single statement" is actually cross
> multiple lines. And checkpatch does not complain this patch.
>
> Well, this is probably a bit personal preference because I feel it has
> better readability with the brackets here.
>
> If you insist on removing the brackets, I can send v2 to do that.
I have no strong preference about it. I'll keep it on maintainers.
You can add my Acked-by: Marek Belisko <marek.belisko@streamunlimited.com>
>
> Regards,
> Axel
>
BR,
marek
next prev parent reply other threads:[~2015-07-24 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 15:22 [PATCH 1/2] ASoC: pcm1681: Fix setting de-emphasis sampling rate selection Axel Lin
2015-07-23 15:23 ` [PATCH 2/2] ASoC: pcm1681: Improve the logic for " Axel Lin
2015-07-23 19:48 ` Marek Belisko
2015-07-24 1:17 ` Axel Lin
2015-07-24 5:22 ` Marek Belisko
2015-07-24 5:48 ` Axel Lin
2015-07-24 12:07 ` Marek Belisko [this message]
2015-07-24 11:31 ` Applied "ASoC: pcm1681: Improve the logic for de-emphasis sampling rate selection" to the asoc tree Mark Brown
2015-07-23 19:46 ` [PATCH 1/2] ASoC: pcm1681: Fix setting de-emphasis sampling rate selection Marek Belisko
2015-07-24 11:31 ` Applied "ASoC: pcm1681: Fix setting de-emphasis sampling rate selection" 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=55B22A94.7000802@streamunlimited.com \
--to=marek.belisko@streamunlimited.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.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