On Thu, Aug 23, 2012 at 10:23:22PM +0200, Geert Uytterhoeven wrote:
Hi Frederic,
On Thu, Aug 23, 2012 at 1:02 PM, Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:
On Wed, Aug 22, 2012 at 07:18:04PM +0200, Geert Uytterhoeven wrote:
On Wed, Aug 22, 2012 at 6:23 PM, Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:
So this fixes some potential RCU stalls in a bunch of architectures.
When rcu_idle_enter()/rcu_idle_exit() became a requirement, we forgot
to handle the architectures that don't support CONFIG_NO_HZ.
I guess the set should be dispatched into arch maintainer trees.
I can take the m68k version, but are you sure you want it this way?
Each of them must be in mainline before they can enter stable.
Yeah, I was thinking the right route is for these patches to be
carried by arch maintainer who then push to Linus and then this goes
to stable.
Is that ok for you?
Otherwise I can carry the patches myself. In a tree of my own, or
Paul's or mmotm. As long as I have your ack.
I applied your patch to the m68k for-3.6/for-linus branch.
I'll ask Linus to pull later in the rc cycle (right now I don't have
anything else
queued for 3.6).
Still, I think it's better to just collect acks and send it to Linus
in one shot,
so it can go into stable in one shot too.
Sure I can do that if you prefer.
Thanks.
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
