linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Nitin Gupta <nitingupta910@gmail.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: Tree for Apr 19 (zcache)
Date: Mon, 23 Apr 2012 21:06:15 -0400	[thread overview]
Message-ID: <20120424010615.GA4393@phenom.dumpdata.com> (raw)
In-Reply-To: <4F91B3C1.5080507@linux.vnet.ibm.com>

On Fri, Apr 20, 2012 at 02:06:41PM -0500, Seth Jennings wrote:
> On 04/20/2012 11:37 AM, Konrad Rzeszutek Wilk wrote:
> > On Thu, Apr 19, 2012 at 11:36:26PM -0500, Seth Jennings wrote:
> >> One fix is this:
> >>
> >> diff --git a/drivers/staging/zcache/Kconfig b/drivers/staging/zcache/Kconfig
> >> index 3ed2c8f..7048e01 100644
> >> --- a/drivers/staging/zcache/Kconfig
> >> +++ b/drivers/staging/zcache/Kconfig
> >> @@ -2,7 +2,7 @@ config ZCACHE
> >>         bool "Dynamic compression of swap pages and clean pagecache pages"
> >>         # X86 dependency is because zsmalloc uses non-portable pte/tlb
> >>         # functions
> >> -       depends on (CLEANCACHE || FRONTSWAP) && CRYPTO && X86
> >> +       depends on (CLEANCACHE || FRONTSWAP) && CRYPTO=y && X86
> >>         select ZSMALLOC
> >>         select CRYPTO_LZO
> >>         default n
> >>
> >> I think this is the best way since ZCACHE is a bool and CRYPTO is the only
> >> one of the dependencies that is a tristate.  This forces both ZSMALLOC and
> >> CRYPTO_LZO to be builtin if ZCACHE is selected.
> >>
> >> Any other suggestions?
> > 
> > Could you do:
> > 
> > default y if (CRYPTO=y || ZSMALLOC=m)
> > default m if (CRYPTO=m || ZSMALLOC=y)
> 
> ZCACHE is a bool and can't be built as a module.

Duh!
> 
> The requirement is the if ZCACHE=y, then ZSMALLOC and
> CRYPTO must also =y.

OK, your patch makes sense then. Can you repost it please with
Greg KH on it so he can add it in the staging tree?

  reply	other threads:[~2012-04-24  1:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  6:46 linux-next: Tree for Apr 19 Stephen Rothwell
2012-04-19 22:26 ` linux-next: Tree for Apr 19 (media/video/mt9m032.c) Randy Dunlap
2012-04-19 23:20   ` Mauro Carvalho Chehab
2012-04-19 22:30 ` linux-next: Tree for Apr 19 (zcache) Randy Dunlap
2012-04-19 22:36   ` Dan Magenheimer
2012-04-19 23:49     ` Seth Jennings
2012-04-20  4:36     ` Seth Jennings
2012-04-20 16:37       ` Konrad Rzeszutek Wilk
2012-04-20 19:06         ` Seth Jennings
2012-04-24  1:06           ` Konrad Rzeszutek Wilk [this message]
2012-04-19 23:15 ` [PATCH -next] nfsd: fix nfs4recover.f printk format warning Randy Dunlap
     [not found]   ` <4F909C78.7000008-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-04-30 19:25     ` [PATCH resend] nfsd: fix nfs4recover.c " Randy Dunlap
     [not found]       ` <4F9EE72B.1020401-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-04-30 21:41         ` J. Bruce Fields

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=20120424010615.GA4393@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nitingupta910@gmail.com \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).