From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: linux-next: manual merge of the tip tree with the kbuild tree Date: Thu, 19 May 2011 23:54:26 -0400 Message-ID: <1305863666.2886.0.camel@fedora> References: <20110520133631.d663013a.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com ([209.132.183.28]:24351 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933275Ab1ETDy4 (ORCPT ); Thu, 19 May 2011 23:54:56 -0400 In-Reply-To: <20110520133631.d663013a.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Sam Ravnborg , Michal Marek On Fri, 2011-05-20 at 13:36 +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in Makefile > between commit 28bc20dccadc ("kbuild: implement several W= levels") from > the kbuild tree and commit 85356f802225 ("kbuild/recordmcount: Add > RECORDMCOUNT_WARN to warn about mcount callers") from the tip tree. > > Just context changes. I fixed it up (see below) and can carry the fix as > necessary. Acked-by: Steven Rostedt -- Steve