From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759821AbZEFNSw (ORCPT ); Wed, 6 May 2009 09:18:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758394AbZEFNSl (ORCPT ); Wed, 6 May 2009 09:18:41 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:53078 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753559AbZEFNSj (ORCPT ); Wed, 6 May 2009 09:18:39 -0400 Date: Wed, 6 May 2009 15:18:24 +0200 From: Ingo Molnar To: Theodore Tso , Christoph Hellwig , linux-kernel@vger.kernel.org, Fr?d?ric Weisbecker , Steven Rostedt , linux-ext4@vger.kernel.org Subject: Re: [PATCH] ext4/jbd2: remove stray markers Message-ID: <20090506131824.GB1325@elte.hu> References: <20090506104436.GA24047@lst.de> <20090506110354.GG25203@elte.hu> <20090506114051.GA4964@mit.edu> <20090506114415.GA26947@lst.de> <20090506125552.GD4964@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090506125552.GD4964@mit.edu> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Theodore Tso wrote: > On Wed, May 06, 2009 at 01:44:15PM +0200, Christoph Hellwig wrote: > > On Wed, May 06, 2009 at 07:40:51AM -0400, Theodore Tso wrote: > > > My complaint with Cristoph's > > > > Christoph, still :) > > Sorry, I keep making that mistake! Keep calling me on it, and > eventually I'll reprogram those finger macros. :-) > > > > Also without Steve's updates you can't actually use them in a module. > > Yep; not sure *how* critical that would be for -next, though. > Probably there would be some complaints.... > > In any case, it'll be less work to worry about patch conflicts if > we just do it during the merge window. If we can just arrange to > push the tip/tracing changes early, I'll push the marker > replacement patches as soon as I see them hit mainline. Cool, thanks! I'll try to aim for an early merge of the tracing tree. (And such dependent patches are generally possible shortly after -rc1 as well, especially if the clean-up factor is significant.) Ingo