From: Fabio Estevam <fabio.estevam@freescale.com>
To: broonie@kernel.org
Cc: Fabio Estevam <fabio.estevam@freescale.com>, alsa-devel@alsa-project.org
Subject: [PATCH 02/18] ASoC: cs42l52: Use IS_ENABLED() macro
Date: Thu, 21 Nov 2013 12:38:39 -0200 [thread overview]
Message-ID: <1385044736-14911-3-git-send-email-fabio.estevam@freescale.com> (raw)
In-Reply-To: <1385044736-14911-1-git-send-email-fabio.estevam@freescale.com>
Using the IS_ENABLED() macro can make the code shorter and simpler.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
sound/soc/codecs/cs42l52.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/soc/codecs/cs42l52.c b/sound/soc/codecs/cs42l52.c
index 8b427c9..19ee10b 100644
--- a/sound/soc/codecs/cs42l52.c
+++ b/sound/soc/codecs/cs42l52.c
@@ -50,7 +50,7 @@ struct cs42l52_private {
u8 mclksel;
u32 mclk;
u8 flags;
-#if defined(CONFIG_INPUT) || defined(CONFIG_INPUT_MODULE)
+#if IS_ENABLED(CONFIG_INPUT)
struct input_dev *beep;
struct work_struct beep_work;
int beep_rate;
@@ -953,7 +953,7 @@ static int cs42l52_resume(struct snd_soc_codec *codec)
return 0;
}
-#if defined(CONFIG_INPUT) || defined(CONFIG_INPUT_MODULE)
+#if IS_ENABLED(CONFIG_INPUT)
static int beep_rates[] = {
261, 522, 585, 667, 706, 774, 889, 1000,
1043, 1200, 1333, 1412, 1600, 1714, 2000, 2182
--
1.8.1.2
next prev parent reply other threads:[~2013-11-21 14:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 14:38 [PATCH 00/18] ASoC: codecs: Use IS_ENABLED() macro Fabio Estevam
2013-11-21 14:38 ` [PATCH 01/18] ASoC: cs4271: " Fabio Estevam
2013-11-27 18:12 ` Mark Brown
2013-11-21 14:38 ` Fabio Estevam [this message]
2013-11-27 18:11 ` [PATCH 02/18] ASoC: cs42l52: " Mark Brown
2013-11-21 14:38 ` [PATCH 03/18] ASoC: da7210: " Fabio Estevam
2013-11-21 14:38 ` Fabio Estevam
2013-11-21 14:38 ` [PATCH 04/18] ASoC: ssm2602: " Fabio Estevam
2013-11-27 18:13 ` Mark Brown
2013-11-21 14:38 ` [PATCH 05/18] ASoC: wm8731: " Fabio Estevam
2013-11-27 18:14 ` Mark Brown
2013-11-21 14:38 ` [PATCH 06/18] ASoC: wm8737: " Fabio Estevam
2013-11-27 18:14 ` Mark Brown
2013-11-21 14:38 ` [PATCH 07/18] ASoC:: wm8741: " Fabio Estevam
2013-11-27 18:15 ` Mark Brown
2013-11-21 14:38 ` [PATCH 08/18] ASoC:: wm8750: " Fabio Estevam
2013-11-27 18:15 ` Mark Brown
2013-11-21 14:38 ` [PATCH 09/18] ASoC: wm8753: " Fabio Estevam
2013-11-27 18:16 ` Mark Brown
2013-11-21 14:38 ` [PATCH 10/18] ASoC: wm8776: " Fabio Estevam
2013-11-21 14:38 ` [PATCH 11/18] ASoC: wm8804: " Fabio Estevam
2013-11-21 14:38 ` [PATCH 12/18] ASoC: wm8900: " Fabio Estevam
2013-11-27 18:19 ` Mark Brown
2013-11-21 14:38 ` [PATCH 13/18] ASoC: wm8983: " Fabio Estevam
2013-11-27 18:20 ` Mark Brown
2013-11-21 14:38 ` [PATCH 14/18] ASoC: wm8985: " Fabio Estevam
2013-11-27 18:20 ` Mark Brown
2013-11-21 14:38 ` [PATCH 15/18] ASoC: wm8988: " Fabio Estevam
2013-11-27 18:21 ` Mark Brown
2013-11-21 14:38 ` [PATCH 16/18] ASoC: wm8990: Fabio Estevam
2013-11-21 14:49 ` Mark Brown
2013-11-21 14:50 ` Fabio Estevam
2013-11-21 18:38 ` Mark Brown
2013-11-21 14:38 ` [PATCH 17/18] ASoC: wm8995: Fabio Estevam
2013-11-21 14:38 ` [PATCH 18/18] AsoC: wm9081: Fabio Estevam
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=1385044736-14911-3-git-send-email-fabio.estevam@freescale.com \
--to=fabio.estevam@freescale.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).