public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Jörn Engel" <joern@logfs.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	logfs@logfs.org
Subject: Re: linux-next -> 2.6.34: Tree for April 28 (logfs)
Date: Tue, 18 May 2010 02:40:48 +0200	[thread overview]
Message-ID: <20100518004048.GF20590@elte.hu> (raw)
In-Reply-To: <20100517193159.GE28003@logfs.org>


* Jörn Engel <joern@logfs.org> wrote:

> On Sun, 16 May 2010 20:48:26 -0700, Randy Dunlap wrote:
> > 
> > This fix is now needed in 2.6.34....
> 
> I didn't send Linus a pull request, as I was on 
> vacation last week.  Bad timing, given the 2.6.34 
> release date. :(

Dont worry about it too much - the likehood of the 
build failure was very low, around 1:50 in my 
randconfig tests. I doubt any real user ran into this 
spontaenously - and randconfig folks know how to fix 
rare build failures :-)

You might still want to forward the commit to 
-stable, once it's in Linus's tree.

Thanks,

	Ingo

  reply	other threads:[~2010-05-18  0:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  6:43 linux-next: Tree for April 28 Stephen Rothwell
2010-04-28 15:56 ` linux-next: Tree for April 28 (logfs) Randy Dunlap
2010-05-05 16:20   ` Randy Dunlap
2010-05-05 20:35     ` Jörn Engel
2010-05-09  6:20       ` Ingo Molnar
2010-05-17  3:48         ` linux-next -> 2.6.34: " Randy Dunlap
2010-05-17 19:31           ` Jörn Engel
2010-05-18  0:40             ` Ingo Molnar [this message]
2010-05-17 19:25         ` linux-next: " Jörn Engel
2010-04-28 17:33 ` [PATCH -next] infiniband: fix cxgb4 printk format warnings Randy Dunlap
2010-05-05 18:57   ` Roland Dreier

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=20100518004048.GF20590@elte.hu \
    --to=mingo@elte.hu \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=logfs@logfs.org \
    --cc=randy.dunlap@oracle.com \
    --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