From: Takashi Iwai <tiwai@suse.de>
To: "Tomer Barletz" <barletz@gmail.com>
Cc: <clemens@ladisch.de>, <perex@perex.cz>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix logical-not-parentheses warning
Date: Sun, 02 Aug 2015 09:10:17 +0200 [thread overview]
Message-ID: <s5hzj2ab1ye.wl-tiwai@suse.de> (raw)
In-Reply-To: <1438494202-30797-1-git-send-email-barletz@gmail.com>
On Sun, 02 Aug 2015 07:43:22 +0200,
Tomer Barletz wrote:
>
> Signed-off-by: Tomer Barletz <barletz@gmail.com>
This is rather a gcc5 problem that doesn't recognize the expression
correctly. Though, this change make things worse, so I'm willing to
take it. But please give the warning message itself in changelog
to show exactly what is the issue. The subject doesn't enough to
understand why this change is needed.
thanks,
Takashi
> ---
> sound/pci/oxygen/oxygen_mixer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/pci/oxygen/oxygen_mixer.c b/sound/pci/oxygen/oxygen_mixer.c
> index 6492bca..4ca1266 100644
> --- a/sound/pci/oxygen/oxygen_mixer.c
> +++ b/sound/pci/oxygen/oxygen_mixer.c
> @@ -88,7 +88,7 @@ static int dac_mute_put(struct snd_kcontrol *ctl,
> int changed;
>
> mutex_lock(&chip->mutex);
> - changed = !value->value.integer.value[0] != chip->dac_mute;
> + changed = (!value->value.integer.value[0]) != chip->dac_mute;
> if (changed) {
> chip->dac_mute = !value->value.integer.value[0];
> chip->model.update_dac_mute(chip);
> --
> 2.4.3
>
>
next prev parent reply other threads:[~2015-08-02 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 5:43 Tomer Barletz
2015-08-02 7:10 ` Takashi Iwai [this message]
2015-08-02 9:08 ` Tomer Barletz
2015-08-02 14:16 ` Joe Perches
2015-08-03 8:15 ` Takashi Iwai
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=s5hzj2ab1ye.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=barletz@gmail.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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
all inboxes | Powered by JetHome®