On Tue, May 3, 2016 at 3:49 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote:
On Tuesday 03 May 2016 15:40:34 Alexandre Belloni wrote:
Queue strategy:
1. These are queued together with Arnd's series,
1. I queue them for v4.7 myself, but then the RTC tree must be mergest
after the m68k tree,
2. I queue them for v4.6.
As I currently don't have any m68k patches queued for v4.7, perhaps it's
easiest if these are included with Arnd's series?
I suggest you take them for 4.7 anyway. I don't think I am confident
enough to merge Arnd's series for 4.7. Also, I doubt I'll get many acks
from some architecture maintainers.
So, my plan is to apply it on top of 4.7-rc1 and let it sit in
linux-next for a while.
Good idea. It's getting a bit late for 4.7 now, and there is nothing
urgent in my series.
OK, I've applied the m68k preparatory fixes and pushed them out.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
