[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200105.141332.1037832872586677248.davem@davemloft.net>
Date: Sun, 05 Jan 2020 14:13:32 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: Jason@...c4.com
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/3] WireGuard bug fixes and cleanups
From: "Jason A. Donenfeld" <Jason@...c4.com>
Date: Thu, 2 Jan 2020 17:47:48 +0100
> I've been working through some personal notes and also the whole git
> repo history of the out-of-tree module, looking for places where
> tradeoffs were made (and subsequently forgotten about) for old kernels.
> The first two patches in this series clean up those. The first one does
> so in the self-tests and self-test harness, where we're now able to
> expand test coverage by a bit, and we're now cooking away tests on every
> commit to both the wireguard-linux repo and to net-next. The second one
> removes a workaround for a skbuff.h bug that was fixed long ago.
> Finally, the last patch in the series fixes in a bug unearthed by newer
> Qualcomm chipsets running the rmnet_perf driver, which does UDP GRO.
Series applied.
I wonder if, for patch #3, we should have a gro cells helper which just
does that list thing and thus makes the situation self documenting.
Powered by blists - more mailing lists