Thread (4 messages) flat view 4 messages, 3 authors, 2016-12-08

Re: net-next closing, README

From: Stephen Hemminger <stephen@networkplumber.org>
Date: 2016-12-08 03:20:26

On Wed, 7 Dec 2016 19:13:45 -0800
Stephen Hemminger [off-list ref] wrote:
On Wed, 07 Dec 2016 16:28:45 -0500 (EST)
David Miller [off-list ref] wrote:
quoted
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.
Never mind, although the changes work on older versions of Windows Server,
the performance would be worse.  Basically old servers don't do UDP checksum
offload but still are capable of handling TCP.  Let me work up a better
solution that handles both cases.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help