From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Xiong Zhou <jencce.kernel@gmail.com>
Cc: Peng Tao <bergwolf@gmail.com>, Jiri Kosina <trivial@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] staging/lustre: add BLOCK depends in Kconfig
Date: Fri, 26 Jul 2013 07:34:05 +0000 [thread overview]
Message-ID: <CE178240.57D7D%andreas.dilger@intel.com> (raw)
In-Reply-To: <CADJHv_tL0R6m2YRu9d6jp3CuwC_z_0SQhpGD8YeAeU4wen98DA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1954 bytes --]
On 2013/07/26 12:54 AM, "Xiong Zhou" <jencce.kernel@gmail.com> wrote:
>2013/7/26 Dilger, Andreas <andreas.dilger@intel.com>:
>> On 2013/07/25 1:06 AM, "Xiong Zhou" <jencce.kernel@gmail.com> wrote:
>>
>>>From: Xiong Zhou <jencce.kernel@gmail.com>
>>>
>>>Add BLOCK depends in Kconfig for LUSTRE to fix this:
>>>drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117
>>>:2
>>>:
>>>error: implicit declaration of function ʽunregister_blkdevʼ
>>>
>>>Signed-off-by: Xiong Zhou <jencce.kernel@gmail.com>
>>>---
>>> drivers/staging/lustre/lustre/Kconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>>diff --git a/drivers/staging/lustre/lustre/Kconfig
>>>b/drivers/staging/lustre/lustre/Kconfig
>>>index 9ae7fa8..0b45de0 100644
>>>--- a/drivers/staging/lustre/lustre/Kconfig
>>>+++ b/drivers/staging/lustre/lustre/Kconfig
>>>@@ -1,6 +1,6 @@
>>> config LUSTRE_FS
>>> tristate "Lustre file system client support"
>>>- depends on STAGING && INET && m
>>>+ depends on STAGING && INET && BLOCK && m
>>> select LNET
>>> select CRYPTO
>>> select CRYPTO_CRC32
>>
>> The Lustre client does not need a block device - it is a network
>> filesystem.
>> The one piece of code that is relevant here relates to a
>>Lustre-optimized
>> "loop" device that bypasses the VFS, data copying, and DLM locking for
>>use
>> by swap and such. It would be better instead to make that code
>>conditional
>> and add a new CONFIG_LUSTRE_LLOOP or similar, and only make that part
>> dependent on BLOCK.
>
>This makes sence. I noticed that this patch has gone into Greg's tree,
>so a coming patch based on this patch is cool?
That would be fine, thanks.
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2013-07-26 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 7:06 [PATCH] staging/lustre: add BLOCK depends in Kconfig Xiong Zhou
2013-07-25 10:52 ` Paul Bolle
2013-07-26 6:03 ` Xiong Zhou
2013-07-25 23:17 ` Dilger, Andreas
2013-07-26 6:54 ` Xiong Zhou
2013-07-26 7:34 ` Dilger, Andreas [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=CE178240.57D7D%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jencce.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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