From: Greg KH <gregkh@linuxfoundation•org>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: linux-next@vger•kernel.org
Subject: Re: staging: zsmalloc appears to break linux-next
Date: Wed, 7 Mar 2012 13:33:39 -0800 [thread overview]
Message-ID: <20120307213339.GA30036@kroah.com> (raw)
In-Reply-To: <CAP=VYLoSR2ygm98jhiVJ8FYTU-cjHvXpJRoNSUPeGdb515tSwQ@mail.gmail.com>
On Tue, Mar 06, 2012 at 08:06:41PM -0500, Paul Gortmaker wrote:
> Hi Greg,
>
> The allmodconfig in linux-next is failing on zsmalloc as follows:
>
> drivers/staging/zsmalloc/zsmalloc-main.c:255: error:
> 'MAX_PHYSMEM_BITS' undeclared (first use in this function)
>
> At 1st glance, it looks to be missing an include of asm/sparsemem.h
>
> Fail log is here:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/5806748/
>
> Apologies if this is something you are aware of already.
No problem, this should be fixed up in the next linux-next release, I
just added some patches that should fix it.
If not, please let me know.
thanks,
greg k-h
prev parent reply other threads:[~2012-03-07 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 1:06 staging: zsmalloc appears to break linux-next Paul Gortmaker
2012-03-07 21:33 ` Greg KH [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=20120307213339.GA30036@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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