From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 0/6] writeback: tracing and fixes V3. Date: Tue, 8 Jun 2010 04:03:25 -0400 Message-ID: <20100608080324.GA3119@infradead.org> References: <1275609328-12514-1-git-send-email-david@fromorbit.com> <20100604074938.GB4448@infradead.org> <20100608001115.GB6965@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com, akpm@linux-foundation.org To: Dave Chinner Return-path: Content-Disposition: inline In-Reply-To: <20100608001115.GB6965@dastard> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Jun 08, 2010 at 10:11:15AM +1000, Dave Chinner wrote: > On Fri, Jun 04, 2010 at 03:49:38AM -0400, Christoph Hellwig wrote: > > > > Not sure what the rules for new tracepoints are, but in addition to the > > fixes I'd really love to see the tracepoints in 2.6.35. > > Personally I think they are just as important (or even more > important) than the bug fixes because we seem to break this code > regularly because nobody can clearly see what the internals are > doing to verify their change is working correctly. Given that Linus is pretty strict about only taking regression fixes I'd rather get the regression fix in and miss out on the tracing until the next merge window then missing out on everything.