mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: gregkh@linuxfoundation.org, dan.magenheimer@oracle.com,
	sjenning@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ramster: depend on CONFIG_NET for sock_* functions
Date: Mon, 07 May 2012 10:43:39 +0200	[thread overview]
Message-ID: <1336380219.1933.16.camel@x61.thuisdomein> (raw)
In-Reply-To: <CA+1xoqcWvJbGgaWt-5XvANH5zZiMXpZVZEQv4cWTr1XHdPu-7Q@mail.gmail.com>

On Mon, 2012-05-07 at 10:29 +0200, Sasha Levin wrote:
> On Mon, May 7, 2012 at 10:10 AM, Paul Bolle <pebolle@tiscali.nl> wrote:
> > On Mon, 2012-05-07 at 10:02 +0200, Sasha Levin wrote:
> >> --- 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 && CONFIG_NET
> >
> > s/CONFIG_NET/NET/ again, I'd say. How was this tested?
> 
> Hm... ran the build again with the patch and noticed it stopped
> complaining, but apparently it wasn't enough.

Well, my guess is that the errors you ran into weren't displayed because
a dependency on an undefined Kconfig symbol (like CONFIG_NET is) will
always fail. Ie, your patch made "RAM capacity sharing" simply disappear
from the build.


Paul Bolle


  reply	other threads:[~2012-05-07  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  8:02 Sasha Levin
2012-05-07  8:10 ` Paul Bolle
2012-05-07  8:29   ` Sasha Levin
2012-05-07  8:43     ` Paul Bolle [this message]
2012-05-07  8:47       ` 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=1336380219.1933.16.camel@x61.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=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®