From: Karim Yaghmour <karim@opersys.com>
To: Greg KH <greg@kroah.com>
Cc: Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Paul Mundt <lethal@linux-sh.org>,
Tom Zanussi <zanussi@us.ibm.com>,
linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: [PATCH, RFC] sysfs: relay channel buffers as sysfs attributes
Date: Wed, 22 Feb 2006 16:27:17 -0500 [thread overview]
Message-ID: <43FCD735.2030002@opersys.com> (raw)
In-Reply-To: <20060221174318.GB23018@kroah.com>
Greg KH wrote:
> And as a debug tool, debugfs seems like the perfict place for it, as you
> have just stated :)
So then the statement is that debugfs is for _ALL_ kinds of debugging,
including application debugging. IOW, anyone considering debugfs as
an fs exclusive to kernel-developers is WRONG. IOW2, distros should
_NOT_ shy away from enabling debugfs by default on their production
kernels.
Right?
Just want to make sure this is clear as it has been my impression
all along (and it seems that of others out there), and I may have
very well been wrong, that debugfs is solely for kernel developers.
Thanks,
Karim
--
President / Opersys Inc.
Embedded Linux Training and Expertise
www.opersys.com / 1.866.677.4546
next prev parent reply other threads:[~2006-02-22 21:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 17:17 [PATCH, RFC] sysfs: relay channel buffers as sysfs attributes Paul Mundt
2006-02-19 17:21 ` Christoph Hellwig
2006-02-19 17:56 ` Greg KH
2006-02-19 18:52 ` Paul Mundt
2006-02-20 5:29 ` Tom Zanussi
2006-02-20 9:20 ` Jens Axboe
2006-02-20 11:17 ` Paul Mundt
2006-02-20 13:05 ` Mathieu Desnoyers
2006-02-20 14:17 ` Christoph Hellwig
2006-02-20 17:15 ` Paul Mundt
2006-02-20 17:37 ` Mathieu Desnoyers
2006-02-20 22:27 ` Greg KH
2006-02-21 15:21 ` Paul Mundt
2006-02-21 16:48 ` Mathieu Desnoyers
2006-02-21 17:43 ` Greg KH
2006-02-22 21:27 ` Karim Yaghmour [this message]
2006-02-22 21:32 ` Greg KH
2006-02-20 22:24 ` Greg KH
2006-02-21 15:10 ` [PATCH] sysfs: Add __ATTR_RELAY() helper for relay attributes Paul Mundt
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=43FCD735.2030002@opersys.com \
--to=karim@opersys.com \
--cc=axboe@suse.de \
--cc=compudj@krystal.dyndns.org \
--cc=greg@kroah.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@us.ibm.com \
/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