From: Matthias Kaehlcke <mka@chromium.org>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Sven Hahne <hahne@zeitkunst.eu>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Grant Grundler <grundler@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>
Subject: [PATCH] ALSA: hda/ca0132: Remove double parentheses
Date: Wed, 15 Mar 2017 15:41:23 -0700 [thread overview]
Message-ID: <20170315224123.175587-1-mka@chromium.org> (raw)
The extra pairs of parantheses are not needed and causes clang to
generate warnings like this:
sound/pci/hda/patch_ca0132.c:1171:14: error: equality comparison with extraneous parentheses [-Werror,-Wparentheses-equality]
if ((buffer == NULL))
~~~~~~~^~~~~~~
sound/pci/hda/patch_ca0132.c:1171:14: note: remove extraneous parentheses around the comparison to silence this warning
if ((buffer == NULL))
~ ^ ~
sound/pci/hda/patch_ca0132.c:1171:14: note: use '=' to turn this equality comparison into an assignment
if ((buffer == NULL))
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
---
sound/pci/hda/patch_ca0132.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/pci/hda/patch_ca0132.c b/sound/pci/hda/patch_ca0132.c
index 11b9b2f17a2e..9cc1bbbbef32 100644
--- a/sound/pci/hda/patch_ca0132.c
+++ b/sound/pci/hda/patch_ca0132.c
@@ -1168,7 +1168,7 @@ static int dspio_write_multiple(struct hda_codec *codec,
int status = 0;
unsigned int count;
- if ((buffer == NULL))
+ if (buffer == NULL)
return -EINVAL;
count = 0;
@@ -1210,7 +1210,7 @@ static int dspio_read_multiple(struct hda_codec *codec, unsigned int *buffer,
unsigned int skip_count;
unsigned int dummy;
- if ((buffer == NULL))
+ if (buffer == NULL)
return -1;
count = 0;
--
2.12.0.367.g23dc2f6d3c-goog
next reply other threads:[~2017-03-15 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 22:41 Matthias Kaehlcke [this message]
2017-03-20 11:55 ` [PATCH] ALSA: hda/ca0132: Remove double parentheses 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=20170315224123.175587-1-mka@chromium.org \
--to=mka@chromium.org \
--cc=Julia.Lawall@lip6.fr \
--cc=alsa-devel@alsa-project.org \
--cc=grundler@chromium.org \
--cc=hahne@zeitkunst.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).