From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2] nfs: fix pnfs Kconfig defaults
Date: Wed, 13 Nov 2013 08:50:33 -0800 [thread overview]
Message-ID: <20131113165033.GA8676@infradead.org> (raw)
In-Reply-To: <20131102102201.GA3860@infradead.org>
Defaulting to m seem to prevent building the pnfs layout modules into the
kernel. Default to the value of CONFIG_NFS_V4 make sure they are
built in for built-in NFSv4 support and modular for a modular NFSv4.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/nfs/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: linux/fs/nfs/Kconfig
===================================================================
--- linux.orig/fs/nfs/Kconfig 2013-11-12 18:42:14.952113008 +0100
+++ linux/fs/nfs/Kconfig 2013-11-13 17:35:24.984154196 +0100
@@ -116,17 +116,17 @@ config NFS_V4_2
config PNFS_FILE_LAYOUT
tristate
depends on NFS_V4_1
- default m
+ default NFS_V4
config PNFS_BLOCK
tristate
depends on NFS_V4_1 && BLK_DEV_DM
- default m
+ default NFS_V4
config PNFS_OBJLAYOUT
tristate
depends on NFS_V4_1 && SCSI_OSD_ULD
- default m
+ default NFS_V4
config NFS_V4_1_IMPLEMENTATION_ID_DOMAIN
string "NFSv4.1 Implementation ID Domain"
prev parent reply other threads:[~2013-11-13 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 10:22 [PATCH] nfs: fix pnfs Kconfig defaults Christoph Hellwig
2013-11-11 20:30 ` Myklebust, Trond
2013-11-11 21:01 ` Christoph Hellwig
2013-11-11 21:04 ` Myklebust, Trond
2013-11-11 21:10 ` Christoph Hellwig
2013-11-13 16:50 ` Christoph Hellwig [this message]
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=20131113165033.GA8676@infradead.org \
--to=hch@infradead.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@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).