From: Shailabh Nagar <nagar@watson.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Gerrit Huizenga <gh@us.ibm.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
Rik van Riel <riel@redhat.com>, Chris Mason <mason@suse.com>,
ckrm-tech <ckrm-tech@lists.sourceforge.net>
Subject: Re: [ckrm-tech] Re: [PATCH] CKRM: 4/10 CKRM: Full rcfs support
Date: Thu, 24 Feb 2005 17:25:51 -0500 [thread overview]
Message-ID: <421E546F.4070505@watson.ibm.com> (raw)
In-Reply-To: <20050224174230.GA10244@kroah.com>
Greg KH wrote:
>
>>>>+config RCFS_FS
>>>>+ tristate "Resource Class File System (User API)"
>>>>+ depends on CKRM
>>>>+ help
>>>>+ RCFS is the filesystem API for CKRM. This separate configuration
>>>>+ option is provided only for debugging and will eventually disappear
>>>>+ since rcfs will be automounted whenever CKRM is configured.
>>>>+
>>>>+ Say N if unsure, Y if you've enabled CKRM, M to debug rcfs
>>>>+ initialization.
>>>>+
>>>
>>>So is this option going to stay around, or should it always be enabled
>>>if CKRM is enabled? Why not just do that for the user?
>>
>>It may be a module, but yes, this should be auto-set in the future when
>>CKRM is enabled.
>
>
> Then fix it? :)
>
> greg k-h
Sounds like a case is being made to make CONFIG_RCFS a "y" and eliminate
the possibility of it being a loadable module ? If so, I don't think its
a good idea. While a kernel may have CKRM enabled, the user may choose
not to use it. In such a case, he should have the option of not loading
the rcfs module.
How does one restrict the choices of a tristate variable to exclude just
the N selection ? It wasn't clear from the kconfig-language.txt...any
pointers appreciated.
-- Shailabh
next prev parent reply other threads:[~2005-02-24 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:48 Gerrit Huizenga
2004-11-29 22:15 ` Greg KH
2005-02-24 9:33 ` Gerrit Huizenga
2005-02-24 9:59 ` Arjan van de Ven
2005-02-24 17:42 ` Greg KH
2005-02-24 22:25 ` Shailabh Nagar [this message]
2005-02-24 23:25 ` [ckrm-tech] " Chris Friesen
2005-02-24 23:59 ` Gerrit Huizenga
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=421E546F.4070505@watson.ibm.com \
--to=nagar@watson.ibm.com \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=riel@redhat.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
Powered by JetHome