[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FABFB7B.9000001@landley.net>
Date: Thu, 10 May 2012 12:31:39 -0500
From: Rob Landley <rob@...dley.net>
To: Ingo Molnar <mingo@...nel.org>
CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Igor Mammedov <imammedo@...hat.com>,
linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, luto@....edu,
suresh.b.siddha@...el.com, avi@...hat.com, johnstul@...ibm.com,
arjan@...ux.intel.com, linux-doc@...r.kernel.org
Subject: Re: [PATCH 0/5] [x86]: Improve secondary CPU bring-up process robustness
On 05/09/2012 08:12 AM, Ingo Molnar wrote:
>
> * Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
>
>> I'm not quite sure how far along he is, but it would be
>> awesome if you could help him out somehow.
>
> bits of Thomas's rework are in latest -tip, the tip:smp/hotplug
> branch, also merged into tip:master and soon to linux-next.
Um, I missed a curve here: I know what linux-next is, and I know what
staging is (although I'm a bit confused about how those two relate), but
what's tip? (Do you mean linux's tree?)
I checked applying-patches.txt and HOWTO in case I missed something, and
both are are hideously stale. (For one thing, both still say 2.6
everywhere. I guess this is my problem now, I'll try a fixup pass this
weekend.)
In the meantime: what do you mean by tip?
> Thanks,
>
> Ingo
>
Rob
--
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation. Pick one.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists