From: Codrut Grosu <codrut.cristian.grosu@gmail.com>
To: perex@perex.cz, tiwai@suse.com
Cc: lgirdwood@gmail.com, broonie@kernel.org, swarren@wwwdotorg.org,
thierry.reding@gmail.com, gnurou@gmail.com, Julia.Lawall@lip6.fr,
nicoleotsuka@gmail.com, alsa-devel@alsa-project.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Codrut Grosu <codrut.cristian.grosu@gmail.com>
Subject: [PATCH] ASoC: tegra: Add blank line after declarations
Date: Sat, 25 Feb 2017 20:59:17 +0200 [thread overview]
Message-ID: <1488049157-6535-1-git-send-email-codrut.cristian.grosu@gmail.com> (raw)
This was reported by checkpatch.pl
Signed-off-by: Codrut GROSU <codrut.cristian.grosu@gmail.com>
---
sound/soc/tegra/tegra20_das.c | 1 +
sound/soc/tegra/tegra30_ahub.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/sound/soc/tegra/tegra20_das.c b/sound/soc/tegra/tegra20_das.c
index 6d4a277..4024e3a 100644
--- a/sound/soc/tegra/tegra20_das.c
+++ b/sound/soc/tegra/tegra20_das.c
@@ -41,6 +41,7 @@ static inline void tegra20_das_write(u32 reg, u32 val)
static inline u32 tegra20_das_read(u32 reg)
{
u32 val;
+
regmap_read(das->regmap, reg, &val);
return val;
}
diff --git a/sound/soc/tegra/tegra30_ahub.c b/sound/soc/tegra/tegra30_ahub.c
index d7494c0..8c10ae7 100644
--- a/sound/soc/tegra/tegra30_ahub.c
+++ b/sound/soc/tegra/tegra30_ahub.c
@@ -41,6 +41,7 @@ static inline void tegra30_apbif_write(u32 reg, u32 val)
static inline u32 tegra30_apbif_read(u32 reg)
{
u32 val;
+
regmap_read(ahub->regmap_apbif, reg, &val);
return val;
}
1.9.1
next reply other threads:[~2017-02-25 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 18:59 Codrut Grosu [this message]
2017-02-27 7:27 ` Thierry Reding
2017-03-07 13:33 ` Applied "ASoC: tegra: Add blank line after declarations" 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=1488049157-6535-1-git-send-email-codrut.cristian.grosu@gmail.com \
--to=codrut.cristian.grosu@gmail.com \
--cc=Julia.Lawall@lip6.fr \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gnurou@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--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
all inboxes | Powered by JetHome®