Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754878Ab1FCNnQ (ORCPT ); Fri, 3 Jun 2011 09:43:16 -0400 Received: from out3.smtp.messagingengine.com ([66.111.4.27]:46562 "EHLO out3.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750990Ab1FCNnO (ORCPT ); Fri, 3 Jun 2011 09:43:14 -0400 X-Sasl-enc: HKj9Iv74mO4MnsTd4mq4Np/K6a2XTTv5zRUCriOadcdk 1307108592 Date: Fri, 3 Jun 2011 22:16:28 +0900 From: Greg KH To: Mitch Harder , dave@jikos.cz, Stephen Rothwell , Chris Mason , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, kreijack@libero.it Subject: Re: linux-next: build warninga in Linus' tree Message-ID: <20110603131628.GB7355@kroah.com> References: <20110530113653.5c7084f0.sfr@canb.auug.org.au> <20110531175709.GC12709@twin.jikos.cz> <20110603111048.GR12709@twin.jikos.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110603111048.GR12709@twin.jikos.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1498 Lines: 38 On Fri, Jun 03, 2011 at 01:10:49PM +0200, David Sterba wrote: > On Wed, Jun 01, 2011 at 10:16:48AM -0500, Mitch Harder wrote: > > I've been playing around with resurrecting the basic sysfs > > capabilities that had been previously incorporated into btrfs. > > > > As it stands right now, it was relatively easy to re-implement sysfs > > as it was originally. However, that implementation of sysfs wasn't > > populated with much information (only total_blocks, blocks_used, and > > blocksize). > > Goffredo Baroncelli (CCed) posted a patch to enhance sysfs interface: > > https://patchwork.kernel.org/patch/308902/ > (http://www.spinics.net/lists/linux-btrfs/msg06777.html) > > > I also had to reverse a small portion of code that was in the last > > clean-up. > > Restoring the code should not be a problem, the cleanup was too eager > and I think a sysfs inteface would be good, not only for debugging > purposes or tuning. > > > If a CONFIG_BTRFS_DEBUG type configuration flag is ever introduced, it > > would be interesting to resurrect btrfs' sysfs capabilities. > > Hearing about CONFIG_BTRFS_DEBUG again, seems worth to add it. For debugging stuff, please use debugfs instead of sysfs, as that is what it is there for. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/