From: Randy Dunlap <rdunlap@infradead.org>
To: hubcap <hubcap@omnibond.com>, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 4/4] Orangefs: wiring and misc
Date: Thu, 01 Jan 2015 09:45:57 -0800 [thread overview]
Message-ID: <54A587D5.2070607@infradead.org> (raw)
In-Reply-To: <1420059225-6832-1-git-send-email-hubcap@logtruck.clemson.edu>
On 12/31/14 12:53, hubcap wrote:
> diff --git a/fs/orangefs/Kconfig b/fs/orangefs/Kconfig
> new file mode 100644
> index 0000000..b600e08
> --- /dev/null
> +++ b/fs/orangefs/Kconfig
> @@ -0,0 +1,7 @@
> +config ORANGEFS_FS
> + tristate "ORANGEFS (Powered by PVFS) support"
> + select FS_POSIX_ACL
> + default y
> + help
> + Orange is a parallel file system designed for use on high end
> + computing (HEC) systems.
Hi,
You need to drop the "default y".
That's not acceptable in the mainline kernel.
--
~Randy
next prev parent reply other threads:[~2015-01-01 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 20:53 [PATCH 4/4] Orangefs: wiring and misc hubcap
2015-01-01 17:45 ` Randy Dunlap [this message]
2015-01-05 19:23 ` [PATCH] Orangefs: Don't compile orangefs by default Mike Marshall
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=54A587D5.2070607@infradead.org \
--to=rdunlap@infradead.org \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).