From: Jason Cooper <jason@lakedaemon.net>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
alsa-devel@alsa-project.org, linux-watchdog@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Chris Ball <chris@printf.net>,
Eduardo Valentin <eduardo.valentin@ti.com>,
Wim Van Sebroeck <wim@iguana.be>,
Gregory Clement <gregory.clement@free-electrons.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 2/4] ARM: dove: prepare new Dove DT Kconfig variable
Date: Fri, 28 Feb 2014 11:34:48 -0500 [thread overview]
Message-ID: <20140228163448.GM1872@titan.lakedaemon.net> (raw)
In-Reply-To: <20140228015310.GC9383@sirena.org.uk>
On Fri, Feb 28, 2014 at 10:53:10AM +0900, Mark Brown wrote:
> On Thu, Feb 27, 2014 at 10:28:03PM +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 to mmc, thermal, wdt, and asoc Kconfigs.
>
> I'd be much happier merging this sort of stuff individually through the
> subsystems, we already have an annoying conflict here... Is there some
> bisection problem with doing that?
shouldn't be. Since these changes || the old with the new config
symbols.
Sebastian, can you split this up into individual patches?
thx,
Jason.
next prev parent reply other threads:[~2014-02-28 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1393536486-3827-1-git-send-email-sebastian.hesselbarth@gmail.com>
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 [this message]
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
2014-03-04 10:32 ` 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=20140228163448.GM1872@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=chris@printf.net \
--cc=eduardo.valentin@ti.com \
--cc=gregory.clement@free-electrons.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=wim@iguana.be \
/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).