From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 00/11] Remove mach-kirkwood
Date: Mon, 19 May 2014 11:30:42 +0200 [thread overview]
Message-ID: <5379CF42.8070306@gmail.com> (raw)
In-Reply-To: <4484941.ZWPK5p5yoC@wuerfel>
On 05/19/2014 11:12 AM, Arnd Bergmann wrote:
> On Friday 16 May 2014 09:59:53 Thomas Petazzoni wrote:
>> Dear Arnd Bergmann,
>>
>> On Thu, 15 May 2014 16:36:35 +0200, Arnd Bergmann wrote:
>>
>>> There are three other series that may or may not make it into 3.16
>>> and that will have conflicts with this one:
>>>
>>> - remove mv78xx0
>>> - remove mach-dove
>>> - convert orion5x to multiplatform
>>
>> The work on Orion5x is still on-going. I'd like to progressively
>> continue the DT migration of Orion5x, moving to multiplatform, and then
>> once it's done, move into mach-mvebu. I'd appreciate to not rush things
>> more than necessary.
>
> Yes, that's fine. I'd just want to be sure we all understand what is
> going into 3.16 and what isn't.
>
> So your plan for now is to do DT support in 3.16 and multiplatform after
> 3.16? That won't have any conflicts with the kirkwood patches then, as
> far as I can tell.
>
> What about dove? Are we ready to remove it or do we give it another
> cycle?
I still have some pending fixes for mmc subsystem. The
ARCH_DOVE/MACH_DOVE patch didn't make it in, and I wasn't able
to get any mmc feedback on 2-3 pings. I'll do a proper RESEND
and see what happens.
So removing legacy dove will definitely _not_ happen for v3.16.
Sebastian
next prev parent reply other threads:[~2014-05-19 9:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 14:23 [PATCH RFC 00/11] Remove mach-kirkwood Andrew Lunn
2014-05-15 14:23 ` [PATCH v3 1/4] ARM: Kirkwood: Add board file for netxbig LEDs Andrew Lunn
2014-05-15 14:38 ` Arnd Bergmann
2014-05-15 20:36 ` Andrew Lunn
2014-05-15 14:23 ` [PATCH v3 2/4] ARM: Kirkwood: Add DT descriptions for net2big and net5big Andrew Lunn
2014-05-15 14:23 ` [PATCH RFC 02/11] sound: ASoC: kirkwood: Remove unused drivers Andrew Lunn
2014-05-26 15:59 ` Mark Brown
2014-05-27 16:45 ` Andrew Lunn
2014-05-27 18:00 ` Mark Brown
2014-05-27 18:18 ` Andrew Lunn
2014-05-27 19:52 ` Mark Brown
2014-05-27 23:46 ` Jason Cooper
2014-05-15 14:23 ` [PATCH v3 3/4] ARM: mvebu: Add LaCie 2Big and 5Big Network v2 Andrew Lunn
2014-05-15 14:23 ` [PATCH RFC 03/11] sound: ASoC: kirkwood: Remove ARCH_KIRKWOOD dependency Andrew Lunn
2014-05-15 22:01 ` Adam Baker
2014-05-15 22:17 ` Andrew Lunn
2014-05-26 15:59 ` Mark Brown
2014-05-15 14:23 ` [PATCH v3 4/4] ARM: multi_v5: Enable LaCie 2Big and 5Big Network v2 Andrew Lunn
2014-05-19 9:05 ` Sebastian Hesselbarth
2014-05-19 14:45 ` Jason Cooper
2014-05-15 14:23 ` [PATCH RFC 04/11] cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency Andrew Lunn
2014-05-15 14:23 ` [PATCH RFC 05/11] ata: " Andrew Lunn
2014-05-15 17:46 ` Tejun Heo
2014-05-15 14:23 ` [PATCH RFC 06/11] thermal: " Andrew Lunn
2014-05-15 14:23 ` [PATCH RFC 07/11] leds: " Andrew Lunn
2014-06-25 23:08 ` Bryan Wu
2014-05-15 14:23 ` [PATCH RFC 08/11] PCI: " Andrew Lunn
2014-05-15 14:23 ` [PATCH RFC 09/11] phy: " Andrew Lunn
2014-05-15 14:23 ` [PATCH RFC 10/11] rtc: " Andrew Lunn
2014-05-15 14:23 ` [PATCH RFC 11/11] watchdog: " Andrew Lunn
2014-05-15 14:36 ` [PATCH RFC 00/11] Remove mach-kirkwood Arnd Bergmann
2014-05-15 14:46 ` Andrew Lunn
2014-05-15 23:08 ` Jason Cooper
2014-05-16 8:18 ` Gregory CLEMENT
2014-05-16 13:01 ` Jason Cooper
2014-05-16 19:09 ` Jason Cooper
2014-05-16 7:59 ` Thomas Petazzoni
2014-05-19 9:12 ` Arnd Bergmann
2014-05-19 9:30 ` Sebastian Hesselbarth [this message]
2014-05-19 9:34 ` Thomas Petazzoni
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=5379CF42.8070306@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--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).