From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: linux-next: manual merge of the tip tree with the kgdb tree Date: Thu, 14 Jan 2010 10:26:00 +0100 Message-ID: <20100114092600.GA13503@elte.hu> References: <20100114161302.285ebe27.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:37350 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756667Ab0ANJ00 (ORCPT ); Thu, 14 Jan 2010 04:26:26 -0500 Content-Disposition: inline In-Reply-To: <20100114161302.285ebe27.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Jason Wessel , Lai Jiangshan , Steven Rostedt , Fr??d??ric Weisbecker * Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in > kernel/trace/trace.c between commit > d304af88a0105ff5b64cffc9108636ecad1fdd78 ("ftrace,kdb: Extend kdb to be > able to dump the ftrace buffer") from the kgdb tree and commit > 7e53bd42d14c75192b99674c40fcc359392da59d ("tracing: Consolidate > protection of reader access to the ring buffer") from the tip tree. Hm, Jason, what is that large commit to kernel/trace/ doing in the KGDB tree, without any apparent acks from the affected people? I dont see it anywhere on lkml nor in my mbox. Please submit it to the affected maintainers - for the Cc: line see the output of: scripts/get_maintainer.pl -f kernel/trace/trace.c Thanks, Ingo