From: Tzung-Bi Shih <tzungbi@google.com>
To: broonie@kernel.org
Cc: tzungbi@google.com, alsa-devel@alsa-project.org
Subject: [PATCH 6/6] ASoC: rt5682: remove unwanted btn_type assignment
Date: Thu, 30 Apr 2020 16:22:31 +0800 [thread overview]
Message-ID: <20200430082231.151127-7-tzungbi@google.com> (raw)
In-Reply-To: <20200430082231.151127-1-tzungbi@google.com>
The following dev_err() is intended to print unexpected btn_type.
Removes the unwanted btn_type assignment.
Signed-off-by: Tzung-Bi Shih <tzungbi@google.com>
---
sound/soc/codecs/rt5682.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/rt5682.c b/sound/soc/codecs/rt5682.c
index 19fb9f1d8f49..5d3b11756a34 100644
--- a/sound/soc/codecs/rt5682.c
+++ b/sound/soc/codecs/rt5682.c
@@ -1134,7 +1134,6 @@ static void rt5682_jack_detect_handler(struct work_struct *work)
case 0x0000: /* unpressed */
break;
default:
- btn_type = 0;
dev_err(rt5682->component->dev,
"Unexpected button code 0x%04x\n",
btn_type);
--
2.26.2.303.gf8c07b1a785-goog
next prev parent reply other threads:[~2020-04-30 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 8:22 [PATCH 0/6] ASoC: rt5682: apply some refactors Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 1/6] ASoC: rt5682: simplify assertions Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 2/6] ASoC: rt5682: fix space issues Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 3/6] ASoC: rt5682: remove empty default case Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 4/6] ASoC: rt5682: replace message printing from pr_() to dev_() Tzung-Bi Shih
2020-04-30 8:22 ` [PATCH 5/6] ASoC: rt5682: remove duplicate rt5682_reset() calls Tzung-Bi Shih
2020-04-30 8:22 ` Tzung-Bi Shih [this message]
2020-04-30 13:40 ` [PATCH 0/6] ASoC: rt5682: apply some refactors 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=20200430082231.151127-7-tzungbi@google.com \
--to=tzungbi@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@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).