From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying toifenslave a second interface to my bond Date: Mon, 04 May 2009 15:44:00 -0700 (PDT) Message-ID: <20090504.154400.07013262.davem@davemloft.net> References: <4086.1241463817@death.nxdomain.ibm.com> <20090504.120651.32573620.davem@davemloft.net> <1241476694.8305.234.camel@psmith-ubeta.netezza.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: fubar@us.ibm.com, netdev@vger.kernel.org To: paul@mad-scientist.net Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:36600 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756235AbZEDWoG (ORCPT ); Mon, 4 May 2009 18:44:06 -0400 In-Reply-To: <1241476694.8305.234.camel@psmith-ubeta.netezza.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Paul Smith Date: Mon, 04 May 2009 18:38:14 -0400 > On Mon, 2009-05-04 at 12:06 -0700, David Miller wrote: >> Greg just posted that there will be no further 2.6.27.x -stable >> releases after the one he just made. > > Really? That seems odd. Everything I heard for the last 7 months or > so, even as late as last month, seemed to imply that 2.6.27 was going to > be the next long-term supported kernel, taking over from 2.6.16, and > that it would be supported for "years". The reality of the situation is that someone has to do the work. > Maybe Adrian is taking over 2.6.27.x maintenance from Greg? I have no idea. > Was this posted on lkml? Yes.