From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Simon <horms@verge.net.au>,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH 0/4] ASoC: simple-card: tidyup unreadable code
Date: Wed, 15 Mar 2017 04:42:43 +0000 [thread overview]
Message-ID: <87mvcncfwx.wl%kuninori.morimoto.gx@renesas.com> (raw)
Hi Mark
These are not a big deal, but tidyup/cleanup unreadable code
on simple-card/simple-scu-card driver.
Kuninori Morimoto (4):
1) ASoC: simple-card: use defined dev on probe()
2) ASoC: simple-scu-card: use defined dev on probe()
3) ASoC: simple-card: add new simple_priv_to_card() macro
4) ASoC: simple-scu-card: add new simple_priv_to_card() macro
sound/soc/generic/simple-card.c | 43 +++++++++++++++++++++----------------
sound/soc/generic/simple-scu-card.c | 37 +++++++++++++++++--------------
2 files changed, 45 insertions(+), 35 deletions(-)
--
1.9.1
next reply other threads:[~2017-03-15 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 4:42 Kuninori Morimoto [this message]
2017-03-15 4:43 ` [PATCH 1/4] ASoC: simple-card: use defined dev on probe() Kuninori Morimoto
2017-03-16 14:11 ` Applied "ASoC: simple-card: use defined dev on probe()" to the asoc tree Mark Brown
2017-03-15 4:43 ` [PATCH 2/4] ASoC: simple-scu-card: use defined dev on probe() Kuninori Morimoto
2017-03-16 14:11 ` Applied "ASoC: simple-scu-card: use defined dev on probe()" to the asoc tree Mark Brown
2017-03-15 4:44 ` [PATCH 3/4] ASoC: simple-card: add new simple_priv_to_card() macro Kuninori Morimoto
2017-03-16 14:11 ` Applied "ASoC: simple-card: add new simple_priv_to_card() macro" to the asoc tree Mark Brown
2017-03-15 4:44 ` [PATCH 4/4] ASoC: simple-scu-card: add new simple_priv_to_card() macro Kuninori Morimoto
2017-03-16 14:10 ` Applied "ASoC: simple-scu-card: add new simple_priv_to_card() macro" 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=87mvcncfwx.wl%kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.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).