From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Marek Subject: Re: linux-next: manual merge of the rr tree with the kbuild tree Date: Fri, 27 Nov 2009 10:37:08 +0100 Message-ID: <4B0F9DC4.1070509@suse.cz> References: <20091127132254.f9b1fc34.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 cantor2.suse.de ([195.135.220.15]:36705 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751862AbZK0JhF (ORCPT ); Fri, 27 Nov 2009 04:37:05 -0500 In-Reply-To: <20091127132254.f9b1fc34.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Rusty Russell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Alan Jenkins , Wenji Huang On 27.11.2009 03:22, Stephen Rothwell wrote: > Hi Rusty, > > Today's linux-next merge of the rr tree got a conflict in > scripts/mod/modpost.c between commit > 36021384778b40ffdd59ab34c275786507ef30a6 ("Kbuild: clear marker out of > modpost") from the kbuild tree and commit > 215143067b9bfacdfd475c5b2fa5536ee30f50ec ("kbuild: sort the list of > symbols exported by the kernel (__ksymtab)") from the rr tree. The "clear marker out of modpost" patch is a no-brainer and when it gets merged doesn't matter that much. Rusty, would you mind moving it to your tree? Alternatively, I can disable it in the kbuild tree for a while so that the two trees don't clash. Michal