From: dannym@scratchpost.org (Danny Milosavljevic)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH v6 0/3] ASoC: sun4i-codec: Distinguish sun4i from sun7i
Date: Sun, 25 Sep 2016 10:08:27 +0200 [thread overview]
Message-ID: <20160925100827.5dc3240d@scratchpost.org> (raw)
In-Reply-To: <20160924200503.10728-1-dannym@scratchpost.org>
The only changes here are the commit summary in the cover letter (it's correct now) and the commit message of patch 1.
I see that the v5 patches 2 and 3 have already been applied in the mean time - and the functional content in v6 is identical.
Therefore, the only thing that needs to be looked at is patch 1 - where I modified the commit message only compared to v5.
Thanks!
next prev parent reply other threads:[~2016-09-25 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 20:05 [PATCH v6 0/3] ASoC: sun4i-codec: Distinguish sun4i from sun7i Danny Milosavljevic
2016-09-24 20:05 ` [PATCH v6 1/3] ASoC: sun4i-codec: Rename sun4i_codec_widgets for consistency Danny Milosavljevic
2016-09-26 8:35 ` Maxime Ripard
2016-09-24 20:05 ` [PATCH v6 2/3] ASoC: sun4i-codec: Rename some sun7i-only registers Danny Milosavljevic
2016-09-24 20:05 ` [PATCH v6 3/3] ASoC: sun4i-codec: Add custom regmap configs Danny Milosavljevic
2016-09-25 8:08 ` Danny Milosavljevic [this message]
2016-09-26 16:33 ` [linux-sunxi] [PATCH v6 0/3] ASoC: sun4i-codec: Distinguish sun4i from sun7i 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=20160925100827.5dc3240d@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=linux-arm-kernel@lists.infradead.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).