From: kbuild test robot <lkp@intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de, lgirdwood@gmail.com,
akshu.agrawal@amd.com, broonie@kernel.org, kbuild-all@01.org
Subject: [RFC PATCH] ASoC: AMD: da7219_dai_clk can be static
Date: Tue, 13 Mar 2018 19:03:53 +0800 [thread overview]
Message-ID: <20180313110353.GA117792@lkp-ib04> (raw)
In-Reply-To: <1520845883-24062-2-git-send-email-akshu.agrawal@amd.com>
Fixes: 7d03b3824d27 ("ASoC: AMD: Enable da7219 master clock using common clock framework")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
acp-da7219-max98357a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/amd/acp-da7219-max98357a.c b/sound/soc/amd/acp-da7219-max98357a.c
index 1441be3..d6e7420 100644
--- a/sound/soc/amd/acp-da7219-max98357a.c
+++ b/sound/soc/amd/acp-da7219-max98357a.c
@@ -42,7 +42,7 @@
#define DUAL_CHANNEL 2
static struct snd_soc_jack cz_jack;
-struct clk *da7219_dai_clk;
+static struct clk *da7219_dai_clk;
static int cz_da7219_init(struct snd_soc_pcm_runtime *rtd)
{
next prev parent reply other threads:[~2018-03-13 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 9:11 [PATCH 1/2] ASoC: AMD: Use single dai for da7219 playback and capture Akshu Agrawal
2018-03-12 9:11 ` [PATCH 2/2] ASoC: AMD: Enable da7219 master clock using common clock framework Akshu Agrawal
2018-03-13 0:32 ` kbuild test robot
2018-03-13 4:37 ` kbuild test robot
2018-03-13 4:37 ` [PATCH] ASoC: AMD: fix returnvar.cocci warnings kbuild test robot
2018-03-13 11:03 ` kbuild test robot [this message]
2018-04-16 17:15 ` Applied "ASoC: amd: acp-da7219-max98357: Make symbol da7219_dai_clk static" to the asoc tree Mark Brown
2018-04-16 17:15 ` Mark Brown
2018-04-26 11:51 ` Mark Brown
2018-03-12 17:01 ` [PATCH 1/2] ASoC: AMD: Use single dai for da7219 playback and capture Mark Brown
2018-03-13 4:26 ` Agrawal, Akshu
2018-03-20 1:21 ` Applied "ASoC: amd: Use single dai for da7219 playback and capture" to the asoc tree 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=20180313110353.GA117792@lkp-ib04 \
--to=lkp@intel.com \
--cc=akshu.agrawal@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.de \
/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).