From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Sasha Levin <levinsasha928@gmail.com>,
gregkh@linuxfoundation.org, dan.magenheimer@oracle.com,
sjenning@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: RE: [PATCH v2] ramster: depend on NET for sock_* functions
Date: Mon, 7 May 2012 07:14:38 -0700 (PDT) [thread overview]
Message-ID: <1eb6ed43-f128-40cd-b9e6-e8578cf7cbdd@default> (raw)
In-Reply-To: <<1336388542-8624-1-git-send-email-levinsasha928@gmail.com>>
> From: Sasha Levin [mailto:levinsasha928@gmail.com]
> Sent: Monday, May 07, 2012 5:02 AM
> To: gregkh@linuxfoundation.org; dan.magenheimer@oracle.com; sjenning@linux.vnet.ibm.com
> Cc: linux-kernel@vger.kernel.org; Sasha Levin
> Subject: [PATCH v2] ramster: depend on NET for sock_* functions
>
> Building ramster without NET would cause linkage issue due to missing
> sock_*() functions in cluster/tcp.c
>
> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
Thanks Sasha!
Acked-by: Dan Magenheimer <dan.magenheimer@oracle.com>
> ---
> drivers/staging/ramster/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/staging/ramster/Kconfig b/drivers/staging/ramster/Kconfig
> index 4af1f8d..8e334cb 100644
> --- a/drivers/staging/ramster/Kconfig
> +++ b/drivers/staging/ramster/Kconfig
> @@ -1,6 +1,6 @@
> config RAMSTER
> bool "Cross-machine RAM capacity sharing, aka peer-to-peer tmem"
> - depends on (CLEANCACHE || FRONTSWAP) && CONFIGFS_FS=y && !ZCACHE && !XVMALLOC && !HIGHMEM
> + depends on (CLEANCACHE || FRONTSWAP) && CONFIGFS_FS=y && !ZCACHE && !XVMALLOC && !HIGHMEM && NET
> select LZO_COMPRESS
> select LZO_DECOMPRESS
> default n
> --
> 1.7.8.5
next parent reply other threads:[~2012-05-07 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1336388542-8624-1-git-send-email-levinsasha928@gmail.com>
2012-05-07 14:14 ` Dan Magenheimer [this message]
2012-05-07 11:02 Sasha Levin
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=1eb6ed43-f128-40cd-b9e6-e8578cf7cbdd@default \
--to=dan.magenheimer@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjenning@linux.vnet.ibm.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
all inboxes | Powered by JetHome®