From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Mark Brown <broonie@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH v5 1/3] ASoC: sun4i-codec: Rename sun4i_codec_widgets for consistency
Date: Fri, 23 Sep 2016 16:02:20 +0300 [thread overview]
Message-ID: <20160923130220.GW8719@lukather> (raw)
In-Reply-To: <20160922071313.12891-2-dannym@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Hi,
On Thu, Sep 22, 2016 at 09:13:11AM +0200, Danny Milosavljevic wrote:
> ASoC: sun4i-codec: Rename "sun4i_codec_widgets" to "sun4i_codec_controls" for
> consistency with the struct field name.
Your commit log still has the flaws your other patches had in the
previous version.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-23 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 7:13 [PATCH v5 0/3] ASoC: sun4i-codec: Distinguish sun4i from sun7i Danny Milosavljevic
2016-09-22 7:13 ` [PATCH v5 1/3] ASoC: sun4i-codec: Rename sun4i_codec_widgets for consistency Danny Milosavljevic
2016-09-23 13:02 ` Maxime Ripard [this message]
2016-09-22 7:13 ` [PATCH v5 2/3] ASoC: sun4i-codec: Rename some sun7i-only registers Danny Milosavljevic
2016-09-22 8:29 ` Maxime Ripard
2016-09-22 7:13 ` [PATCH v5 3/3] ASoC: sun4i-codec: Add custom regmap configs Danny Milosavljevic
2016-09-22 8:29 ` Maxime Ripard
2016-09-25 5:58 ` Applied "ASoC: sun4i-codec: Add custom regmap configs" to the asoc tree Mark Brown
2016-09-22 8:31 ` [PATCH v5 0/3] ASoC: sun4i-codec: Distinguish sun4i from sun7i Maxime Ripard
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=20160923130220.GW8719@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dannym@scratchpost.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wens@csie.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).