From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id AA64AB713B for ; Thu, 11 Jun 2009 08:26:31 +1000 (EST) Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id E3253DDD04 for ; Thu, 11 Jun 2009 08:26:30 +1000 (EST) Subject: Re: [PATCH 00/33] My PS3-specific patches for 2.6.31 From: Benjamin Herrenschmidt To: Nate Case In-Reply-To: <1244671205.29684.1611.camel@localhost.localdomain> References: <1244644748-24211-1-git-send-email-Geert.Uytterhoeven@sonycom.com> <1244670213.3352.11.camel@pasglop> <1244671205.29684.1611.camel@localhost.localdomain> Content-Type: text/plain Date: Thu, 11 Jun 2009 08:26:25 +1000 Message-Id: <1244672785.3352.16.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2009-06-10 at 17:00 -0500, Nate Case wrote: > Hmm, I guess this sorta answers my question to Kumar about my recent > -next submissions being eligible for 2.6.31. Sorry for not paying > closer attention -- I just assumed we weren't even close to the cutoff > time. I didn't even see Kumar's "next" branch until April 30th > (around -rc6..rc7 time I think). > Your patches may still make it, we'll see. Kumar was away for a week just before the merge window and I started this round's next branch a bit late, so we can be flexible, it depends how many patches are involved, how invasive or risky they are etc... In your case, I'll let Kumar judge. However, in Geert case, it's a pile of 33 patches sent after the break point, which is a bit too much over the top :-) Cheers, Ben.