From: Mark Brown <broonie@kernel.org>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] ASoC: kirkwood: prepare new Dove DT Kconfig variable
Date: Tue, 4 Mar 2014 12:03:14 +0800 [thread overview]
Message-ID: <20140304040314.GC2411@sirena.org.uk> (raw)
In-Reply-To: <1393662801-17950-1-git-send-email-sebastian.hesselbarth@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
On Sat, Mar 01, 2014 at 09:33:17AM +0100, Sebastian Hesselbarth wrote:
> DT-enabled Dove will move over from ARCH_DOVE in mach-dove to MACH_DOVE in
> mach-mvebu. As non-DT ARCH_DOVE will stay to rot for a while, add a new
> DT-only MACH_DOVE Kconfig.
This doesn't apply against current ASoC, please check and resend.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-04 4:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 21:28 [PATCH 0/4] ARM: dove: move Dove DT to MVEBU Sebastian Hesselbarth
2014-02-27 21:28 ` [PATCH 1/4] ARM: dove: add system controller node Sebastian Hesselbarth
2014-03-04 4:00 ` Jason Cooper
2014-02-27 21:28 ` [PATCH 2/4] ARM: dove: prepare new Dove DT Kconfig variable Sebastian Hesselbarth
2014-02-27 21:51 ` Wim Van Sebroeck
2014-02-27 22:05 ` Sebastian Hesselbarth
2014-02-28 1:53 ` Mark Brown
2014-02-28 16:34 ` Jason Cooper
2014-02-28 18:12 ` Sebastian Hesselbarth
2014-03-01 8:33 ` [PATCH v2 1/5] ASoC: kirkwood: " Sebastian Hesselbarth
2014-03-04 4:01 ` Jason Cooper
2014-03-04 4:03 ` Mark Brown [this message]
2014-03-04 10:32 ` Sebastian Hesselbarth
2014-03-01 8:33 ` [PATCH v2 2/5] watchdog: orion: " Sebastian Hesselbarth
2014-03-02 14:25 ` Wim Van Sebroeck
2014-03-04 4:02 ` Jason Cooper
2014-03-01 8:33 ` [PATCH v2 3/5] thermal: dove: " Sebastian Hesselbarth
2014-03-04 4:03 ` Jason Cooper
2014-03-20 5:57 ` Zhang Rui
2014-03-01 8:33 ` [PATCH v2 4/5] mmc: " Sebastian Hesselbarth
2014-03-04 4:03 ` Jason Cooper
2014-03-27 15:24 ` Sebastian Hesselbarth
2014-04-15 18:20 ` Sebastian Hesselbarth
2014-03-01 8:33 ` [PATCH v2 5/5] phy: mvebu-sata: " Sebastian Hesselbarth
2014-03-01 13:38 ` Kishon Vijay Abraham I
2014-03-02 20:47 ` Sebastian Hesselbarth
2014-03-04 4:04 ` Jason Cooper
2014-02-27 21:28 ` [PATCH 3/4] ARM: mvebu: move DT Dove to MVEBU Sebastian Hesselbarth
2014-02-27 21:40 ` Jason Cooper
2014-02-27 21:43 ` Sebastian Hesselbarth
2014-02-27 21:47 ` Jason Cooper
2014-02-27 22:03 ` [PATCH v2 " Sebastian Hesselbarth
2014-03-01 8:39 ` [PATCH v3 " Sebastian Hesselbarth
2014-03-04 4:29 ` Jason Cooper
2014-02-27 21:28 ` [PATCH 4/4] ARM: add Marvell Dove and some drivers to multi_v7 defconfig Sebastian Hesselbarth
2014-03-04 4:07 ` Jason Cooper
2014-03-17 15:29 ` Jason Cooper
2014-03-17 19:03 ` Arnd Bergmann
2014-02-27 21:45 ` [PATCH 0/4] ARM: dove: move Dove DT to MVEBU Jason Cooper
2014-02-27 21:48 ` Sebastian Hesselbarth
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=20140304040314.GC2411@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.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;
as well as URLs for NNTP newsgroup(s).