From: Andrew Morton <akpm@linux-foundation.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [next:akpm 72/246] mm/vmscan.c:1787:10: error: 'struct zone' has no member named 'compact_order_
Date: Fri, 07 Sep 2012 08:07:30 +0000 [thread overview]
Message-ID: <20120907010730.09495427.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120907075535.GA18981@localhost>
On Fri, 7 Sep 2012 15:55:35 +0800 Fengguang Wu <fengguang.wu@intel.com> wrote:
> Hi Mel,
>
> FYI, kernel build failed on
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
> head: d28e1f373a79e532eecbe6b17beeb4d2052c1a52
> commit: 038b615836d456496d321156271e47881469c8fd [72/246] mm: vmscan: scale number of pages reclaimed by reclaim/compaction based on failures
> config: i386-randconfig-k925 (attached as .config)
>
> All related error/warning messages:
>
> mm/vmscan.c: In function 'should_continue_reclaim':
> mm/vmscan.c:1787:10: error: 'struct zone' has no member named 'compact_order_failed'
> mm/vmscan.c:1788:32: error: 'struct zone' has no member named 'compact_defer_shift'
hm, Does that tree not include
http://ozlabs.org/~akpm/mmotm/broken-out/mm-vmscan-scale-number-of-pages-reclaimed-by-reclaim-compaction-based-on-failures-fix.patch
?
Perhaps that linux-next is using the previous mm - I did a new release
earlier today.
next prev parent reply other threads:[~2012-09-07 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 7:55 [next:akpm 72/246] mm/vmscan.c:1787:10: error: 'struct zone' has no member named 'compact_order_fail Fengguang Wu
2012-09-07 8:07 ` Andrew Morton [this message]
2012-09-07 8:10 ` [next:akpm 72/246] mm/vmscan.c:1787:10: error: 'struct zone' has no member named 'compact_order_ Fengguang Wu
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=20120907010730.09495427.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kernel-janitors@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 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.