From: Vladimir Zapolskiy <vz@mleia.com>
To: Trent Piepho <tpiepho@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Axel Lin <axel.lin@ingics.com>, Takashi Iwai <tiwai@suse.de>,
Linus Walleij <linus.walleij@linaro.org>,
patches@opensource.wolfsonmicro.com,
Liam Girdwood <lgirdwood@gmail.com>,
linux-gpio <linux-gpio@vger.kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Subject: Re: [alsa-devel] [PATCH 5/7] ASoC: wm5100: remove bitwise operations involving GPIO level value
Date: Thu, 04 Jun 2015 01:58:37 +0300 [thread overview]
Message-ID: <556F869D.6060601@mleia.com> (raw)
In-Reply-To: <CA+7tXigF6LginxQGUBKqLZorecPp7B8wydzDA4jb4iKOi7CdBA@mail.gmail.com>
Hello Trent,
On 04.06.2015 00:51, Trent Piepho wrote:
> On Wed, Jun 3, 2015 at 12:13 PM, Vladimir Zapolskiy <vz@mleia.com> wrote:
>>>
>>> BTW, with a little C algebra:
>>> const unsigned int val = value ? 0x1 << WM5100_GP1_LVL_SHIFT : 0;
>>> const unsigned int val = (value ? 0x1 : 0) << WM5100_GP1_LVL_SHIFT;
>>> const unsigned int val = (!!value) << WM5100_GP1_LVL_SHIFT; //
>>> definition of ! operator
>>>
>>> And now we're back to where we started, so I don't really see why this
>>> is even necessary. The semantics of the ! operator will be changed in a
>>> future C version?
>>
>> I don't think it makes sense to discuss technical aspects of the
>> proposed change, as I mentioned in the discussion yesterday I see no
>> technical issues at this point, and my changes are described as
>> nonfunctional.
>>
>> The _nontechnical_ problem I see (well, may be I'm just blowing it up)
>> is a Linux kernel code style policy problem, to my knowledge the policy
>> of using bitwise and arithmetic operations on bool type variables and
>> constants is not defined, and since the policy is not yet defined I'm
>> glad to take part in its discussion now.
>
> I don't believe this is the case.
please excuse me for possible misunderstanding, you don't believe that
I'm interested in discussing a _nontechnical_ problem stated above?
> From C99, section 6.5.3.3, paragraph 5:
C99 is a strict superset over Linux coding style (e.g. remember //
comments or "register" specifier), so let's forget about.
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2015-06-03 22:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 23:07 [PATCH 0/7] ASoC: remove bitwise operations on GPIO level value Vladimir Zapolskiy
2015-06-01 23:09 ` [PATCH 1/7] ASoC: rt5677: add GPIO helper macros Vladimir Zapolskiy
2015-06-02 5:23 ` Takashi Iwai
2015-06-01 23:09 ` [PATCH 2/7] ASoC: rt5677: clean up gpiolib callbacks Vladimir Zapolskiy
2015-06-02 19:38 ` Mark Brown
2015-06-02 20:39 ` Vladimir Zapolskiy
2015-06-02 20:50 ` Mark Brown
2015-06-02 21:54 ` Vladimir Zapolskiy
2015-06-03 11:38 ` Mark Brown
2015-06-01 23:09 ` [PATCH 3/7] ASoC: wm8903: generalize GPIO control register bits Vladimir Zapolskiy
2015-06-02 9:19 ` Charles Keepax
2015-06-04 8:30 ` Linus Walleij
2015-06-04 8:47 ` [alsa-devel] " Charles Keepax
2015-06-04 9:19 ` Mark Brown
2015-06-04 9:24 ` Charles Keepax
2015-06-04 10:34 ` Mark Brown
2015-06-01 23:09 ` [PATCH 4/7] ASoC: wm8903: simplify gpiolib callbacks Vladimir Zapolskiy
2015-06-02 8:38 ` Charles Keepax
2015-06-02 19:41 ` Mark Brown
2015-06-02 20:18 ` Vladimir Zapolskiy
2015-06-02 20:31 ` Mark Brown
2015-06-02 20:41 ` Vladimir Zapolskiy
2015-06-01 23:09 ` [PATCH 5/7] ASoC: wm5100: remove bitwise operations involving GPIO level value Vladimir Zapolskiy
2015-06-02 8:40 ` Charles Keepax
2015-06-02 19:45 ` Mark Brown
2015-06-02 20:23 ` Vladimir Zapolskiy
2015-06-02 20:36 ` Mark Brown
2015-06-02 20:58 ` Vladimir Zapolskiy
2015-06-03 10:50 ` Trent Piepho
2015-06-03 11:07 ` Mark Brown
2015-06-03 19:13 ` [alsa-devel] " Vladimir Zapolskiy
2015-06-03 21:51 ` Trent Piepho
2015-06-03 22:58 ` Vladimir Zapolskiy [this message]
2015-06-01 23:09 ` [PATCH 6/7] ASoC: wm8962: " Vladimir Zapolskiy
2015-06-02 8:41 ` Charles Keepax
2015-06-01 23:09 ` [PATCH 7/7] ASoC: wm8996: " Vladimir Zapolskiy
2015-06-02 8:43 ` Charles Keepax
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=556F869D.6060601@mleia.com \
--to=vz@mleia.com \
--cc=acourbot@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=tiwai@suse.de \
--cc=tpiepho@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.