All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: build failure after merge of the final tree (tip tree related)
Date: Tue, 3 Aug 2010 07:29:11 +0200	[thread overview]
Message-ID: <20100803052911.GA25362@elte.hu> (raw)
In-Reply-To: <1280799724.1902.84.camel@pasglop>


* Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:

> > Please, no, don't break the memblock code now.  I'm not reworking the
> > ARM implementation just as the merge window has opened - especially
> > as the ARM implementation has now been pulled into other people's
> > trees.
> > 
> > If there's changes to memblock which haven't been in linux-next (which,
> > as this is a new failure, that is most definitely the case), then they
> > shouldn't be going into this merge window.
> 
> I'm happy to wait and sit on the memblock churn until after ARM's in.
> 
> I can then fixup my patches.

Ok, i've zapped it all from -tip.

Thanks,

	Ingo

  parent reply	other threads:[~2010-08-03  5:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 16:23 linux-next: build failure after merge of the final tree (tip tree related) Stephen Rothwell
2010-08-02 16:28 ` Russell King
2010-08-02 16:32   ` H. Peter Anvin
2010-08-03  1:07     ` Benjamin Herrenschmidt
2010-08-03  1:42   ` Benjamin Herrenschmidt
2010-08-03  3:13     ` H. Peter Anvin
2010-08-03  4:32       ` Benjamin Herrenschmidt
2010-08-03  5:29     ` Ingo Molnar [this message]
2010-08-02 16:28 ` Stephen Rothwell
2010-08-03  1:41 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2011-04-12  4:00 Stephen Rothwell
2011-04-12  6:20 ` Ingo Molnar
2011-04-12  6:25   ` David Miller
2010-11-29  2:50 Stephen Rothwell
2010-11-29 22:30 ` Peter Zijlstra
2010-12-07  1:56 ` Stephen Rothwell
2010-11-22  2:39 Stephen Rothwell
2010-11-22 22:00 ` Don Zickus
2010-11-29  2:50 ` Stephen Rothwell
2010-11-29  8:29   ` Ingo Molnar
2010-11-29 14:30     ` Don Zickus
2010-12-07  1:58       ` Stephen Rothwell
2010-12-07 15:37         ` Don Zickus
2010-10-14  5:49 Stephen Rothwell
2010-10-14  6:31 ` Ingo Molnar
2010-09-13 14:29 Stephen Rothwell
2010-09-16  6:32 ` Stephen Rothwell
2010-09-16  6:39   ` Ingo Molnar
2010-09-16  7:08     ` Russell King - ARM Linux
2010-09-16  7:34       ` Ingo Molnar
2010-09-16  9:02         ` Russell King - ARM Linux
2010-09-16  7:09     ` Stephen Rothwell
2010-09-16  7:20       ` Yinghai Lu
2010-09-16  7:27         ` Stephen Rothwell
2010-09-13 14:06 Stephen Rothwell
2010-09-13 19:17 ` Matt Fleming
2010-09-13 19:22   ` Peter Zijlstra
2010-06-23 16:31 Stephen Rothwell
2010-06-23 16:55 ` Frederic Weisbecker
2010-06-23 23:31   ` Stephen Rothwell
2010-06-24  0:37     ` Stephen Rothwell
2010-06-23  0:50 Stephen Rothwell

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=20100803052911.GA25362@elte.hu \
    --to=mingo@elte.hu \
    --cc=benh@kernel.crashing.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rmk@arm.linux.org.uk \
    --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.