From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: linux-next: manual merge of the percpu tree with Linus' tree Date: Fri, 30 Oct 2009 11:02:25 +0100 Message-ID: <4AEAB9B1.4000304@kernel.org> References: <20091030192050.06a0f706.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from hera.kernel.org ([140.211.167.34]:39458 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754074AbZJ3KDX (ORCPT ); Fri, 30 Oct 2009 06:03:23 -0400 In-Reply-To: <20091030192050.06a0f706.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Rusty Russell , Christoph Lameter , Ingo Molnar , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Jiri Kosina Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the percpu tree got a conflict in mm/percpu.c > between commit 403a91b1659cb149dbddc5885f892734ae4542d8 ("percpu: allow > pcpu_alloc() to be called with IRQs off") from Linus' tree and commit > 0f5e4816dbf38ce9488e611ca2296925c1e90d5e ("percpu: remove some sparse > warnings") from the percpu tree. > > I fixed it up (see below) and can carry the fix as necessary. I'll pull master into for-next in a few days so that we can do sparse cleanup pass over the whole tree on the latest tree. Thanks. -- tejun