All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Nick Piggin <npiggin@suse.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: linux-next: Tree for March 16 (slob)
Date: Tue, 17 Mar 2009 10:29:02 +0100	[thread overview]
Message-ID: <20090317092902.GA6477@elte.hu> (raw)
In-Reply-To: <20090317111129.5bf04ae6.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> On Mon, 16 Mar 2009 11:32:00 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> >
> > mm/slob.c:480: error: 'flags' undeclared (first use in this function)
> > 
> > pseudo-patch:
> > 
> > s/flags/gfp/
> 
> Caused by commit cf40bd16fdad42c053040bcd3988f5fdedbb6c57 ("lockdep:
> annotate reclaim context (__GFP_NOFS)") from the tracing tree.
> 
> Now fixed in the tip tree.

Note this has been broken for a relatively long time and only 
got fixed when i noticed that randconfig was not as random as it 
was supposed to be. That's how it started triggering in 
linux-next too i suspect.

	Ingo

  reply	other threads:[~2009-03-17  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 11:06 linux-next: Tree for March 16 Stephen Rothwell
2009-03-16 18:32 ` linux-next: Tree for March 16 (slob) Randy Dunlap
2009-03-17  0:11   ` Stephen Rothwell
2009-03-17  9:29     ` Ingo Molnar [this message]
2009-03-18 15:49       ` Randy Dunlap

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=20090317092902.GA6477@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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.