From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nitin Gupta <ngupta@vflare.org>,
Robert Jennings <rcj@linux.vnet.ibm.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Autif Khan <autif.mlist@gmail.com>
Subject: Re: [PATCH] drivers: staging: zcache: fix Kconfig crypto dependency
Date: Tue, 24 Apr 2012 08:30:28 -0500 [thread overview]
Message-ID: <4F96AAF4.2000402@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120424022702.GA6573@kroah.com>
On 04/23/2012 09:27 PM, Greg Kroah-Hartman wrote:
> Ok, this fixes one of the build problems reported, what about the other
> one?
Both problems that I heard about were caused by same issue;
the issue fixed in this patch.
ZSMALLOC=m was only allowed because CRYPTO=m was allowed.
This patch requires CRYPTO=y, which also requires ZSMALLOC=y
when ZCACHE=y.
https://lkml.org/lkml/2012/4/19/588
https://lkml.org/lkml/2012/4/23/481
Thanks,
Seth
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nitin Gupta <ngupta@vflare.org>,
Robert Jennings <rcj@linux.vnet.ibm.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Autif Khan <autif.mlist@gmail.com>
Subject: Re: [PATCH] drivers: staging: zcache: fix Kconfig crypto dependency
Date: Tue, 24 Apr 2012 08:30:28 -0500 [thread overview]
Message-ID: <4F96AAF4.2000402@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120424022702.GA6573@kroah.com>
On 04/23/2012 09:27 PM, Greg Kroah-Hartman wrote:
> Ok, this fixes one of the build problems reported, what about the other
> one?
Both problems that I heard about were caused by same issue;
the issue fixed in this patch.
ZSMALLOC=m was only allowed because CRYPTO=m was allowed.
This patch requires CRYPTO=y, which also requires ZSMALLOC=y
when ZCACHE=y.
https://lkml.org/lkml/2012/4/19/588
https://lkml.org/lkml/2012/4/23/481
Thanks,
Seth
next prev parent reply other threads:[~2012-04-24 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 1:33 [PATCH] drivers: staging: zcache: fix Kconfig crypto dependency Seth Jennings
2012-04-24 1:33 ` Seth Jennings
2012-04-24 2:09 ` Konrad Rzeszutek Wilk
2012-04-24 2:09 ` Konrad Rzeszutek Wilk
2012-04-24 2:27 ` Greg Kroah-Hartman
2012-04-24 2:27 ` Greg Kroah-Hartman
2012-04-24 13:30 ` Seth Jennings [this message]
2012-04-24 13:30 ` Seth Jennings
2012-04-24 14:35 ` Greg Kroah-Hartman
2012-04-24 14:35 ` Greg Kroah-Hartman
2012-04-28 0:38 ` Randy Dunlap
2012-04-28 0:38 ` Randy Dunlap
2012-05-03 21:11 ` Dan Magenheimer
2012-05-03 21:11 ` Dan Magenheimer
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=4F96AAF4.2000402@linux.vnet.ibm.com \
--to=sjenning@linux.vnet.ibm.com \
--cc=autif.mlist@gmail.com \
--cc=dan.magenheimer@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=rcj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.