From: Greg KH <gregkh@linuxfoundation.org>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: konrad.wilk@oracle.com, raghavendra.kt@linux.vnet.ibm.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xen/debugfs: Check debugfs initialization before using it
Date: Mon, 9 Dec 2013 10:40:50 -0800 [thread overview]
Message-ID: <20131209184050.GC28986@kroah.com> (raw)
In-Reply-To: <CABawtvNUBwTVzFfR4UotCexARN4+As5wKEPyGmRzN7-xZ6J00w@mail.gmail.com>
On Mon, Dec 09, 2013 at 09:42:23PM +0800, Ethan Zhao wrote:
> Greg,
> I am the man who built a Xen dom0, but couldn't see debugfs
> directory and files as expected. there is no warning or tip for me to
> enable the CONFIG_DEBUG_FS=y in .config , it cost me minutes to figure
> out what's
> the matter. and I know should check defugfs config and initialization as
> zswap_debugfs, tracer_debugfs ,rproc_debugfs did. Is it useless ? if
> it could save me just 1 minute next time ?
So you would want a "warning" showing up for every single part of the
kernel that uses debugfs for when it isn't enabled? That doesn't make
too much sense now, does it?
If you need/want debugfs then enable it in the kernel build, it's not
that hard, right?
greg k-h
next prev parent reply other threads:[~2013-12-09 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 11:31 [PATCH] xen/debugfs: Check debugfs initialization before using it ethan.zhao
2013-12-08 14:01 ` Greg KH
2013-12-09 1:43 ` Ethan Zhao
2013-12-09 8:25 ` Greg KH
2013-12-09 8:44 ` Ethan Zhao
2013-12-09 8:55 ` Greg KH
2013-12-09 9:57 ` Ethan Zhao
2013-12-09 11:17 ` Greg KH
2013-12-09 13:42 ` Ethan Zhao
2013-12-09 18:40 ` Greg KH [this message]
2013-12-10 8:03 ` Ethan Zhao
2013-12-10 8:19 ` Greg KH
2013-12-11 2:31 ` Ethan Zhao
-- strict thread matches above, loose matches on Subject: below --
2013-12-09 10:04 Ethan Zhao
2013-12-09 11:18 ` Greg KH
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=20131209184050.GC28986@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ethan.kernel@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raghavendra.kt@linux.vnet.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