From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: hooanon05@yahoo.co.jp, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: Q. DEBUG_FS and SYSFS config (Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs)
Date: Tue, 24 Mar 2009 16:57:16 +0100 [thread overview]
Message-ID: <ac3eb2510903240857l2b072ffay7c3e2e5683527a4f@mail.gmail.com> (raw)
In-Reply-To: <20090324153329.GA13705@kroah.com>
On Tue, Mar 24, 2009 at 16:33, Greg KH <greg@kroah.com> wrote:
>> First, configure "normaly".
>> General setup
>> [ ] Configure standard kernel features (for small systems) --->
>>
>> $ egrep -i '(sysfs|debug_fs)' .config
>> CONFIG_SYSFS_DEPRECATED=y
>> CONFIG_SYSFS_DEPRECATED_V2=y
>
> You should disable those two options, no modern distro needs them
> anymore.
In fact, all recent distros will no longer work correctly, because
DEPRECATED disables features which are expected to be there today. I
guess it's time to remove the *_V2 hack to reset the default value,
and set the default of CONFIG_SYSFS_DEPRECATED=n?
Thanks,
Kay
next prev parent reply other threads:[~2009-03-24 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 5:12 [RFC Aufs2 #3 0/2] 'debug' module parm and /sys/fs/aufs entries J. R. Okajima
2009-03-19 5:12 ` [RFC Aufs2 #3 1/2] replace /sys/fs/aufs/debug by /sys/module/aufs/parmaters/debug J. R. Okajima
2009-03-19 5:12 ` [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs J. R. Okajima
2009-03-20 0:45 ` Greg KH
2009-03-20 2:25 ` hooanon05
2009-03-20 2:42 ` Greg KH
2009-03-20 2:55 ` hooanon05
2009-03-20 3:06 ` Greg KH
2009-03-20 3:59 ` hooanon05
2009-03-20 4:18 ` Greg KH
2009-03-20 5:15 ` hooanon05
2009-03-20 5:44 ` Greg KH
2009-03-24 8:16 ` Q. DEBUG_FS and SYSFS config (Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs) hooanon05
2009-03-24 15:33 ` Greg KH
2009-03-24 15:57 ` Kay Sievers [this message]
2009-03-24 23:20 ` 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=ac3eb2510903240857l2b072ffay7c3e2e5683527a4f@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=greg@kroah.com \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).