linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Greg KH <greg@kroah.com>
Cc: gregkh@suse.de, Chris Mason <chris.mason@oracle.com>,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	matthew@wil.cx, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	ngupta@vflare.org, jeremy@goop.org,
	Kurt Hackel <kurt.hackel@oracle.com>,
	npiggin@kernel.dk, riel@redhat.com,
	Konrad Wilk <konrad.wilk@oracle.com>,
	mel@csn.ul.ie, minchan.kim@gmail.com,
	kosaki.motohiro@jp.fujitsu.com, sfr@canb.auug.org.au,
	wfg@mail.ustc.edu.cn, tytso@mit.edu, viro@ZenIV.linux.org.uk,
	hughd@google.com, hannes@cmpxchg.org
Subject: RE: [PATCH V1 3/3] drivers/staging: kztmem: misc build/config
Date: Tue, 8 Feb 2011 08:30:57 -0800 (PST)	[thread overview]
Message-ID: <e908a602-35b8-4ecc-aad2-8973da171161@default> (raw)
In-Reply-To: <20110204212843.GA18924@kroah.com>

> From: Greg KH [mailto:greg@kroah.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, 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>

      parent reply	other threads:[~2011-02-08 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 17:21 Dan Magenheimer
2011-02-04 21:28 ` Greg KH
2011-02-04 22:17   ` Dan Magenheimer
2011-02-08 16:30   ` Dan Magenheimer [this message]

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=e908a602-35b8-4ecc-aad2-8973da171161@default \
    --to=dan.magenheimer@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew@wil.cx \
    --cc=mel@csn.ul.ie \
    --cc=minchan.kim@gmail.com \
    --cc=ngupta@vflare.org \
    --cc=npiggin@kernel.dk \
    --cc=riel@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=wfg@mail.ustc.edu.cn \
    /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