From: Andrew Morton <akpm@linux-foundation.org>
To: Valdis.Kletnieks@vt.edu
Cc: Anton Blanchard <anton@samba.org>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: mmotm 2010-09-22 - build error in drivers/staging/zram
Date: Wed, 22 Sep 2010 20:43:05 -0700 [thread overview]
Message-ID: <20100922204305.2fdc5b66.akpm@linux-foundation.org> (raw)
In-Reply-To: <56264.1285212366@localhost>
On Wed, 22 Sep 2010 23:26:06 -0400 Valdis.Kletnieks@vt.edu wrote:
> On Wed, 22 Sep 2010 16:12:09 PDT, akpm@linux-foundation.org said:
> > The mm-of-the-moment snapshot 2010-09-22-16-11 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
>
> Looks like zram-free-percpu-data-on-module-exit.patch has issues:
>
> CC [M] drivers/staging/zram/zram_drv.o
> drivers/staging/zram/zram_drv.c: In function 'zram_reset_device':
> drivers/staging/zram/zram_drv.c:500:2: error: incompatible type for argument 1 of 'free_percpu'
> include/linux/percpu.h:153:13: note: expected 'void *' but argument is of type 'struct zram_stats'
> make[3]: *** [drivers/staging/zram/zram_drv.o] Error 1
>
bah. `make allmodconfig' enables CONFIG_STAGING_EXCLUDE_BUILD, so
nothing under staging gets built. Seems rather dumb.
zram-free-percpu-data-on-module-exit.patch seems to be unneeded in the
current zram driver - I'll drop the patch, thanks.
next prev parent reply other threads:[~2010-09-23 3:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 23:12 mmotm 2010-09-22-16-11 uploaded akpm
2010-09-23 3:26 ` mmotm 2010-09-22 - build error in drivers/staging/zram Valdis.Kletnieks
2010-09-23 3:43 ` Andrew Morton [this message]
2010-09-23 4:21 ` Greg KH
2010-09-23 4:26 ` Andrew Morton
2010-09-23 6:04 ` Stephen Rothwell
2010-09-23 17:29 ` Randy Dunlap
2010-09-23 17:51 ` mmotm 2010-09-22-16-11 uploaded (staging/spectra) Randy Dunlap
2010-09-27 9:34 ` i915 flickering [was: mmotm 2010-09-22-16-11 uploaded] Jiri Slaby
2010-09-27 15:25 ` Jiri Slaby
2010-09-27 9:36 ` i915: glxgears causes GPU hang " Jiri Slaby
2010-09-27 9:51 ` Chris Wilson
2010-09-29 8:33 ` Jiri Slaby
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=20100922204305.2fdc5b66.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=anton@samba.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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