From: Ben Evans <bevans@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] CONFIG_PROC_FS
Date: Mon, 28 Aug 2017 19:52:41 +0000 [thread overview]
Message-ID: <D5C9ECC8.DCEE%jevans@cray.com> (raw)
I see that this flag is set for all kernels, and from what I can tell, will always be on. Is there a reason that anyone knows of to keep it and the related #ifdef's?
I'm guessing that this is a holdover from the days were non-linux builds were still being considered.
-Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20170828/4e52c58b/attachment.htm>
next reply other threads:[~2017-08-28 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 19:52 Ben Evans [this message]
2017-08-28 20:02 ` [lustre-devel] CONFIG_PROC_FS Patrick Farrell
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=D5C9ECC8.DCEE%jevans@cray.com \
--to=bevans@cray.com \
--cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.