[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161020.145344.2118760258546112762.davem@davemloft.net>
Date: Thu, 20 Oct 2016 14:53:44 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jarod@...hat.com
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/9] net: use core MTU range checking
everywhere
From: Jarod Wilson <jarod@...hat.com>
Date: Thu, 20 Oct 2016 13:55:15 -0400
> This stack of patches should get absolutely everything in the kernel
> converted from doing their own MTU range checking to the core MTU range
> checking. This second spin includes alterations to hopefully fix all
> concerns raised with the first, as well as including some additional
> changes to drivers and infrastructure where I completely missed necessary
> updates.
>
> These have all been built through the 0-day build infrastructure via the
> (rebasing) master branch at https://github.com/jarodwilson/linux-muck, which
> at the time of the most recent compile across 147 configs, was based on
> net-next at commit 7b1536ef0aa0.
Series applied, hopefully this gets most of the fallout.
Thanks Jarod.
Powered by blists - more mailing lists