RFC Remove mach-kirkwood
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 11 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 11 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 00/11] Remove mach-kirkwood
Quoted 20 lines · Arnd Bergmann
Quoted 7 lines · On Friday 16 May 2014 09:59:53 Thomas Petazzoni wrote:
Dear Arnd Bergmann,
Quoted 3 lines · Arnd Bergmann
There are three other series that may or may not make it into 3.16 and that will have conflicts with this one:
Quoted 8 lines
Quoted 3 lines
- remove mv78xx0
- remove mach-dove
- convert orion5x to multiplatformThe 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.
Quoted 6 lines
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