[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57C9024A16AD2D4C97DC78E552063EA3E29CCB18@orsmsx505.amr.corp.intel.com>
Date: Tue, 22 Sep 2009 14:24:30 -0700
From: "Luck, Tony" <tony.luck@...el.com>
To: "Luck, Tony" <tony.luck@...el.com>, Ingo Molnar <mingo@...e.hu>,
Tejun Heo <tj@...nel.org>
CC: Nick Piggin <npiggin@...e.de>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
linux-ia64 <linux-ia64@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Christoph Lameter <cl@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCHSET percpu#for-next] percpu: convert ia64 to dynamic
percpu and drop the old one
I just noticed the "#for-next" in the Subject line for these
patches. Do they depend on some stuff in linux-next that is
not in Linus' tree (pulled today HEAD=7fa07729e...)? If so, then
ignore my results.
Kernel built from generic_defconfig does boot OK though, so I suspect
this is a discontig vs. contig problem.
-Tony
--
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