linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andi Kleen <andi@firstfloor.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: linux-next: Tree for December 9 (hwpoison)
Date: Wed, 9 Dec 2009 18:25:55 +0100	[thread overview]
Message-ID: <20091209172555.GG18989@one.firstfloor.org> (raw)
In-Reply-To: <20091209090921.a3293706.rdunlap@xenotime.net>

On Wed, Dec 09, 2009 at 09:09:21AM -0800, Randy Dunlap wrote:
> On Wed, 9 Dec 2009 17:47:38 +1100 Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > My usual call for calm: please do not put stuff destined for 2.6.34 into
> > linux-next trees until after 2.6.33-rc1.
> > 
> > Changes since 20091208:
> > 
> > 
> > The hwpoison tree lost its build failure.
> 
> 
> CONFIG_PROC_PAGE_MONITOR is not enabled:
> 
> 
> mm/built-in.o: In function `hwpoison_filter':
> (.text+0x43cce): undefined reference to `stable_page_flags'

Thanks. Fengguang fixed that already, but I haven't pushed out 
an update tree yet. Will do soon.
-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2009-12-09 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091209174738.3b8c28a6.sfr@canb.auug.org.au>
2009-12-09 17:09 ` Randy Dunlap
2009-12-09 17:25   ` Andi Kleen [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=20091209172555.GG18989@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox