[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e908a602-35b8-4ecc-aad2-8973da171161@default>
Date: Tue, 8 Feb 2011 08:30:57 -0800 (PST)
From: Dan Magenheimer <dan.magenheimer@...cle.com>
To: Greg KH <greg@...ah.com>
Cc: gregkh@...e.de, Chris Mason <chris.mason@...cle.com>,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
matthew@....cx, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
ngupta@...are.org, jeremy@...p.org,
Kurt Hackel <kurt.hackel@...cle.com>, npiggin@...nel.dk,
riel@...hat.com, Konrad Wilk <konrad.wilk@...cle.com>,
mel@....ul.ie, minchan.kim@...il.com,
kosaki.motohiro@...fujitsu.com, sfr@...b.auug.org.au,
wfg@...l.ustc.edu.cn, tytso@....edu, viro@...IV.linux.org.uk,
hughd@...gle.com, hannes@...xchg.org
Subject: RE: [PATCH V1 3/3] drivers/staging: kztmem: misc build/config
> From: Greg KH [mailto:greg@...ah.com]
> 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.
Thanks,
Dan
[1] https://lkml.org/lkml/2011/2/5/181
[2] https://lkml.org/lkml/2011/2/6/346
https://lkml.org/lkml/2011/2/6/345
https://lkml.org/lkml/2011/2/6/344
https://lkml.org/lkml/2011/2/6/343
[3] http://www.kroah.com/log/linux/linux-staging-update.html
[4] http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git
[5] http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-2.6.git;a=shortlog;h=refs/heads/staging-next
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists