From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: net-next closing, README Date: Wed, 7 Dec 2016 19:13:45 -0800 Message-ID: <20161207191345.6e765651@xeon-e3> References: <20161207.162845.1424733568267357691.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: David Miller Return-path: Received: from mail-pg0-f45.google.com ([74.125.83.45]:32889 "EHLO mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752887AbcLHDVi (ORCPT ); Wed, 7 Dec 2016 22:21:38 -0500 Received: by mail-pg0-f45.google.com with SMTP id 3so168990564pgd.0 for ; Wed, 07 Dec 2016 19:21:38 -0800 (PST) In-Reply-To: <20161207.162845.1424733568267357691.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 07 Dec 2016 16:28:45 -0500 (EST) David Miller wrote: > The merge window is about to open soon, and next week I will be > having sporadic internet access while travelling around, therefore > I am closing net-next up tonight. > > Therefore, please do not submit any new features or cleanups for > net-next. Bug fixes for problems introduced in net-next are fine, > however. > > Thank you. I have a couple of patches that I would like to get into net-next, but it is not critical. They replace the hardcoded workarounds with code that negotiates values with the host. Would these be acceptable? Sorry for the delay but needed to test on oldest supported version to ensure negotiation worked.