From: Paul Bolle <pebolle@tiscali.nl>
To: Koro Chen <koro.chen@mediatek.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
srv_heupstream@mediatek.com, tiwai@suse.de,
linux-kernel@vger.kernel.org, s.hauer@pengutronix.de,
lgirdwood@gmail.com, robh+dt@kernel.org, broonie@kernel.org,
linux-mediatek@lists.infradead.org, galak@codeaurora.org,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [alsa-devel] [PATCH 1/3] ASoC: mediatek: Add AFE platform driver
Date: Fri, 12 Jun 2015 09:37:57 +0200 [thread overview]
Message-ID: <1434094677.2271.125.camel@x220> (raw)
In-Reply-To: <1434074158.10969.5.camel@mtksdaap41>
On Fri, 2015-06-12 at 09:55 +0800, Koro Chen wrote:
> On Thu, 2015-06-11 at 09:03 +0200, Paul Bolle wrote:
> > (What does negating a bool twice do?)
> >
> Because bool actually can be unsigned char, although actually in this
> driver, the caller always passes "true" or "false" to this function.
bool is _Bool in the kernel (see include/linux/types.h). So whenever you
see a bool in the kernel you can assume it's either 0 or 1. Are there
any cases where this conveniently simple rule doesn't hold?
But here the discussion is moot, because as you say, the function will
only be passed false or true so we know "enable" is either 0 or 1 and
double negating will do nothing.
> Do you think if this is the case, should I still need to do !!?
So you should not, as it's confusing at best.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-06-12 7:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 14:24 [PATCH 0/3] ASoC: Mediatek: Add support for MT8173 SoC Koro Chen
2015-06-10 14:24 ` [PATCH 2/3] ASoC: mediatek: Add machine driver for MAX98090 codec Koro Chen
[not found] ` <1433946276-25969-3-git-send-email-koro.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-06-12 13:13 ` Mark Brown
[not found] ` <20150612131325.GA1921-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-15 2:31 ` Koro Chen
[not found] ` <1433946276-25969-1-git-send-email-koro.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-06-10 14:24 ` [PATCH 1/3] ASoC: mediatek: Add AFE platform driver Koro Chen
2015-06-11 7:03 ` Paul Bolle
2015-06-11 7:13 ` Paul Bolle
2015-06-12 1:55 ` [alsa-devel] " Koro Chen
2015-06-12 7:37 ` Paul Bolle [this message]
2015-06-12 8:24 ` Koro Chen
[not found] ` <1433946276-25969-2-git-send-email-koro.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-06-12 13:06 ` Mark Brown
[not found] ` <20150612130638.GZ1921-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-15 2:06 ` Koro Chen
2015-06-10 14:24 ` [PATCH 3/3] ASoC: mediatek: Add machine driver for rt5650 rt5676 codec Koro Chen
2015-06-12 13:15 ` 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=1434094677.2271.125.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=koro.chen@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
--cc=tiwai@suse.de \
/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).