From: Nicolin Chen <nicoleotsuka@gmail.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"timur@kernel.org" <timur@kernel.org>,
"Xiubo.Lee@gmail.com" <Xiubo.Lee@gmail.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"S.j. Wang" <shengjiu.wang@nxp.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"festevam@gmail.com" <festevam@gmail.com>
Subject: Re: [EXT] Re: [PATCH V1] ASoC: fsl_esai: replace fall-through with break
Date: Mon, 8 Apr 2019 20:54:52 -0700 [thread overview]
Message-ID: <20190409035450.GA8476@Asurada> (raw)
In-Reply-To: <eba6372b-618c-4633-f0a9-06c034cf2f9c@embeddedor.com>
Hi Gustavo,
On Mon, Apr 08, 2019 at 10:20:25PM -0500, Gustavo A. R. Silva wrote:
> >>> diff --git a/sound/soc/fsl/fsl_esai.c b/sound/soc/fsl/fsl_esai.c index
> >>> c7410bbfd2af..bad0dfed6b68 100644
> >>> --- a/sound/soc/fsl/fsl_esai.c
> >>> +++ b/sound/soc/fsl/fsl_esai.c
> >>> @@ -251,7 +251,7 @@ static int fsl_esai_set_dai_sysclk(struct
> >> snd_soc_dai *dai, int clk_id,
> >>> break;
> >>> case ESAI_HCKT_EXTAL:
> >>> ecr |= ESAI_ECR_ETI;
> >>
> >> Also, you should use a simple assignment operator "=" instead of "|=" in
> >> both cases.
> >
> > The result is same for "=" and "|=", because there is "ecr = 0" in beginning of
> > This function.
> >
>
> Following that same logic, then why not use "+=" instead?
>
> The point is: is "|=" or any other assignment operator other than "=" necessary?
> The answer in this case is: no, it is not. So, go for the simple one and avoid
> any unnecessary confusion.
I would like to keep "|=" here, just in case that someday it'd be easier
to insert something to ecr before this chunk. So please get easy on this
one.
Thanks
Nicolin
next prev parent reply other threads:[~2019-04-09 3:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 9:28 [PATCH V1] ASoC: fsl_esai: replace fall-through with break S.j. Wang
2019-04-08 15:55 ` Gustavo A. R. Silva
2019-04-09 2:54 ` [EXT] " S.j. Wang
2019-04-09 3:20 ` Gustavo A. R. Silva
2019-04-09 3:54 ` Nicolin Chen [this message]
2019-04-10 2:39 ` S.j. Wang
2019-04-10 3:51 ` Nicolin Chen
2019-04-10 3:52 ` Nicolin Chen
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=20190409035450.GA8476@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=gustavo@embeddedor.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=shengjiu.wang@nxp.com \
--cc=timur@kernel.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;
as well as URLs for NNTP newsgroup(s).