Messages in this thread | | | From | David Brownell <> | Subject | Re: [linux-usb-devel] [RFC PATCH] debugfs - yet another in-kernel file system | Date | Fri, 10 Dec 2004 18:02:00 -0800 |
| |
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
- 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/
| |