Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938386AbcJRPes (ORCPT ); Tue, 18 Oct 2016 11:34:48 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:42946 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935436AbcJRPek (ORCPT ); Tue, 18 Oct 2016 11:34:40 -0400 Date: Tue, 18 Oct 2016 11:34:38 -0400 (EDT) Message-Id: <20161018.113438.62003626132979588.davem@davemloft.net> To: jarod@redhat.com Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH net-next 00/15] ethernet: use core min/max MTU checking From: David Miller In-Reply-To: <20161017195417.48259-1-jarod@redhat.com> References: <20161017195417.48259-1-jarod@redhat.com> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 18 Oct 2016 08:34:39 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 768 Lines: 17 From: Jarod Wilson Date: Mon, 17 Oct 2016 15:54:02 -0400 > Now that the network stack core min/max MTU checking infrastructure is in > place, time to start making drivers use it. We'll start with the easiest > ones, the ethernet drivers, split roughly by vendor, with a catch-all > patch at the end. > > For the most part, every patch does the same essential thing: removes the > MTU range checking from the drivers' ndo_change_mtu function, puts those > ranges into the core net_device min_mtu and max_mtu fields, and where > possible, removes ndo_change_mtu functions entirely. > > These patches have all been built through the 0-day build infrastructure > provided by Intel, on top of net-next as of October 17. Series applied, thanks Jarod.