From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Nitin Gupta <ngupta@vflare.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: linux-next: Tree for Feb 13 (staging/zsmalloc)
Date: Mon, 13 Feb 2012 09:46:01 -0800 [thread overview]
Message-ID: <4F394C59.2000604@xenotime.net> (raw)
In-Reply-To: <20120213172613.be7258c4c34431ff31dcbbef@canb.auug.org.au>
On 02/12/2012 10:26 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120210:
zsmalloc-main.c should #include <linux/mmzone.h> to fix this build error:
drivers/staging/zsmalloc/zsmalloc-main.c: In function 'obj_location_to_handle':
drivers/staging/zsmalloc/zsmalloc-main.c:254:32: error: 'MAX_PHYSMEM_BITS' undeclared (first use in this function)
drivers/staging/zsmalloc/zsmalloc-main.c: In function 'obj_handle_to_location':
drivers/staging/zsmalloc/zsmalloc-main.c:266:10: error: 'MAX_PHYSMEM_BITS' undeclared (first use in this function)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-02-13 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 6:26 linux-next: Tree for Feb 13 Stephen Rothwell
2012-02-13 17:46 ` Randy Dunlap [this message]
2012-02-13 17:51 ` linux-next: Tree for Feb 13 (ata/libata-acpi.c) Randy Dunlap
2012-02-13 18:00 ` linux-next: Tree for Feb 13 (staging/zsmalloc 2) Randy Dunlap
2012-02-13 18:11 ` linux-next: Tree for Feb 13 (sound/soc) Randy Dunlap
2012-02-13 22:10 ` linux-next: Tree for Feb 13 Grant Likely
2012-02-13 23:01 ` Nicholas A. Bellinger
2012-02-13 23:43 ` Stephen Rothwell
2012-02-13 23:32 ` Jack Stone
2012-02-13 23:56 ` Jack Stone
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=4F394C59.2000604@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=sfr@canb.auug.org.au \
/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.