public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [RFC PATCH] debugfs - yet another in-kernel file system
Date: Fri, 10 Dec 2004 18:02:00 -0800	[thread overview]
Message-ID: <200412101802.00197.david-b@pacbell.net> (raw)
In-Reply-To: <20041211013930.GB12846@kroah.com>

On Friday 10 December 2004 5:39 pm, Greg KH wrote:
> > 
> > The problem with sysfs here is:  no seq_file support.
> > Otherwise it solves the basic "where to put the debug
> > files associated with "device X" or "driver Y" problems
> > in a good non-confusing way:  there are directories
> > already set up for devices and for drivers.
> 
> Yes, but that's a design decision for sysfs.  no seq_file support is a
> feature, not a shortcoming :)

It's an arbitrary fiat, sure; not a feature!  ;)


> > What I'd really want out of a debug file API is to resolve
> > the naming issues, work with seq_file, and "softly and
> > silently vanish away".  I think this patch has the last
> > two, but not the first one!
> 
> I considered adding a kobject as a paramater to the debugfs interface.
> The file created would be equal to the path that the kobject has.  Would
> that work for you?

If I could pass device->kobj or driver->kobj, that'd be good.
Will there be a /debug/devices tree parallel to /sys/devices?

- Dave


  reply	other threads:[~2004-12-11  2:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  0:50 [RFC PATCH] debugfs - yet another in-kernel file system Greg KH
2004-12-10  0:55 ` [RFC PATCH] convert uhci-hcd to use debugfs Greg KH
2004-12-10 14:15   ` Josh Boyer
2004-12-10 15:27     ` Greg KH
2004-12-10 16:21       ` Josh Boyer
2004-12-10 17:17         ` Comments on new kernel dev. model Peter Karlsson
2004-12-10 23:44           ` Greg KH
2004-12-10  7:07 ` [RFC PATCH] debugfs - yet another in-kernel file system Jan Engelhardt
2004-12-10  7:54   ` Greg KH
2004-12-10  8:00     ` Jan Engelhardt
2004-12-10 16:02       ` Greg KH
2004-12-10 14:46 ` Josh Boyer
2004-12-10 15:30   ` Greg KH
2004-12-10 16:26     ` Josh Boyer
2004-12-10 17:21 ` Jörn Engel
2004-12-10 17:35   ` Greg KH
2004-12-10 18:29     ` Jörn Engel
2004-12-10 19:38 ` Roland Dreier
2004-12-11  1:29 ` [linux-usb-devel] " David Brownell
2004-12-11  1:39   ` Greg KH
2004-12-11  2:02     ` David Brownell [this message]
2004-12-11  2:05       ` Greg KH
2004-12-11  2:26     ` Roland Dreier
2004-12-11  2:32       ` Greg KH
2004-12-11 13:23         ` Roland Dreier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200412101802.00197.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox