From: Dominik Brodowski <linux@dominikbrodowski.net>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org, Pavel Machek <pavel@ucw.cz>
Subject: [OT] debugfs and sysfs [Was: Re: RE: on-ness]
Date: Fri, 21 Apr 2006 21:04:48 +0200 [thread overview]
Message-ID: <20060421190448.GA15324@isilmar.linta.de> (raw)
In-Reply-To: <200604211200.45959.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
On Fri, Apr 21, 2006 at 12:00:45PM -0700, David Brownell wrote:
> > Uh, there's a rule "one-value-per-file" for sysfs. Arrays might be OK in
> > certain cases, but lots of system-specific information in one file? No way,
> > IMHO.
>
> Remember that sysfs != debugfs, and /sys/kernel/debug is debugfs.
Sorry, missed that bit. Editing my fstab right now :)
> (And for that matter, binary
> data in sysfs is more than one-value-per-file ... there are plenty of cases
> where that "rule" doesn't need to be obeyed.)
Binary data is special, indeed, but needs to be rare -- and I sincerely
doubt there are "plenty of cases" for sysfs where this rule doesn't need to
be obeyed, but that would be OT now...
Thanks,
Dominik
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-04-21 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 18:39 RE: on-ness Brown, Len
2006-04-20 13:25 ` Pavel Machek
2006-04-21 15:27 ` David Brownell
2006-04-21 15:40 ` Dominik Brodowski
2006-04-21 17:03 ` David Brownell
2006-04-21 17:12 ` Dominik Brodowski
2006-04-21 18:30 ` David Brownell
2006-04-21 18:33 ` Dominik Brodowski
2006-04-21 19:00 ` David Brownell
2006-04-21 19:04 ` Dominik Brodowski [this message]
2006-04-21 19:01 ` Pavel Machek
2006-04-24 21:04 ` David Brownell
2006-04-24 21:32 ` Pavel Machek
2006-04-24 23:21 ` David Brownell
2006-04-21 17:15 ` David Brownell
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=20060421190448.GA15324@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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