From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261738AbULJQFF (ORCPT ); Fri, 10 Dec 2004 11:05:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261751AbULJQEK (ORCPT ); Fri, 10 Dec 2004 11:04:10 -0500 Received: from mail.kroah.org ([69.55.234.183]:24298 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S261750AbULJQCt (ORCPT ); Fri, 10 Dec 2004 11:02:49 -0500 Date: Fri, 10 Dec 2004 08:02:24 -0800 From: Greg KH To: Jan Engelhardt Cc: linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] debugfs - yet another in-kernel file system Message-ID: <20041210160224.GA6714@kroah.com> References: <20041210005055.GA17822@kroah.com> <20041210075429.GA30223@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 10, 2004 at 09:00:22AM +0100, Jan Engelhardt wrote: > >> I have to admit that adding another filesystem that is very like procfs or > >> sysfs make some kind of redundancy. > > > >Why? The main issue is the discussion usually goes like this: > > > >Me: Hey, the /proc/driver/foo/foo_value really shouldn't be in proc. > >Developer: Ok, but it has a lot of really good debug stuff in it. Can > >I put it in sysfs? > >Me: No, sysfs is for one-value-per-file whenever possible. It needs to > >go somewhere else. > >Developer: Well, if you don't have anywhere else to put it, why are you > >even bringing this up at all. Go away and leave me alone. > > So how about adding seqfiles (or multi-value-per-file things) to sysfs? No, that is not going to happen, as it is directly opposite to how sysfs is supposed to work (one _single_ value per file). thanks, greg k-h