lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 8 Feb 2011 08:30:57 -0800 (PST)
From:	Dan Magenheimer <>
To:	Greg KH <>
Cc:, Chris Mason <>,,,,,,,,
	Kurt Hackel <>,,, Konrad Wilk <>,,,,,,,,,
Subject: RE: [PATCH V1 3/3] drivers/staging: kztmem: misc build/config

> From: Greg KH []
> Subject: Re: [PATCH V1 3/3] drivers/staging: kztmem: misc build/config
> On Tue, Jan 18, 2011 at 09:21:51AM -0800, Dan Magenheimer wrote:
> > [PATCH V1 3/3] drivers/staging: kztmem: misc build/config
> >
> > Makefiles and Kconfigs to build kztmem in drivers/staging
> >
> > There is a dependency on xvmalloc.* which in 2.6.37 resides
> > in drivers/staging/zram.  Should this move or disappear,
> > some Makefile/Kconfig changes will be required.
> There is some other kind of dependancy as well, because I get the
> following errors when building:
> : 
> If you require a kbuild dependancy, then put it in your Kconfig file
> please, don't break the build.
> I'll not apply these patches for now until that's fixed up.
> thanks,
> greg k-h

Hi Greg --

Just wanted to confirm that this is now fixed and hope that you
can now apply BUT note that per agreement with Nitin Gupta [1]
the patchset has been modified to be named zcache and the
renamed patchset (with the proper kbuild dependency) has been
posted at [2].

ALSO, could you please confirm the path by which this patchset
will find its way upstream?  I see from your blog [3] that after
you apply it, I should be able to see it in sfr's linux-next
tree [4] which IIUC sfr pulls regularly from your staging-next
tree [5].  And I think at the next merge window, YOU will
provide the pull request to Linus included with any other
staging drivers?  Is this all correct?

Sorry for the driver-staging-newbie question but your blog
entry is 2 years old and I'd like to (1) ensure that I don't
drop some important task *I* still need to do and (2) be able
to track the progress of zcache through the various trees as
a self-educational exercise.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists