From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [net-next 0/5] bnx2x enhancements and date update Date: Sun, 20 Mar 2011 13:47:50 -0700 (PDT) Message-ID: <20110320.134750.104058019.davem@davemloft.net> References: <1300638963.17303.29.camel@lb-tlvb-dmitry> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, eilong@broadcom.com, vladz@broadcom.com To: dmitry@broadcom.com Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:60807 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752384Ab1CTUrM (ORCPT ); Sun, 20 Mar 2011 16:47:12 -0400 In-Reply-To: <1300638963.17303.29.camel@lb-tlvb-dmitry> Sender: netdev-owner@vger.kernel.org List-ID: From: "Dmitry Kravkov" Date: Sun, 20 Mar 2011 18:36:03 +0200 > Please consider applying following patch series to the "net-next". Please consider paying attention to announcements I make about what is appropriate to submit at this point in time: http://marc.info/?l=linux-netdev&m=130023005214910&w=2 By the time I open up the net-next-2.6 tree and am actually willing to apply patches, something you submit now might not even apply cleanly. That's why I don't want people submitting net-next-2.6 patches at this time. It also is distracting to submit such patches at this time. All efforts should be placed on regression fixing and closing out the merge window cleanly.