From: David Miller <davem@davemloft.net>
To: tlfalcon@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, brking@linux.vnet.ibm.com,
marcelo.leitner@gmail.com, pradeeps@linux.vnet.ibm.com,
jmaxwell37@gmail.com, zdai@us.ibm.com, eric.dumazet@gmail.com
Subject: Re: [PATCH net v3] ibmveth: set correct gso_size and gso_type
Date: Sat, 10 Dec 2016 15:56:47 -0500 (EST) [thread overview]
Message-ID: <20161210.155647.1988856288960520451.davem@davemloft.net> (raw)
In-Reply-To: <1481395188-9137-1-git-send-email-tlfalcon@linux.vnet.ibm.com>
From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Date: Sat, 10 Dec 2016 12:39:48 -0600
> v3: include a check for non-zero mss when calculating gso_segs
>
> v2: calculate gso_segs after Eric Dumazet's comments on the earlier patch
> and make sure everyone is included on CC
I already applied v1 which made it all the way even to Linus's
tree. So you'll have to send me relative fixups if there are
things to fix or change since v1.
You must always generate patches against the current 'net' tree.
next prev parent reply other threads:[~2016-12-10 20:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 0:09 [PATCH net-next] ibmveth: v1 calculate correct gso_size and set gso_type Jon Maxwell
2016-10-27 14:44 ` Thomas Falcon
2016-10-27 15:26 ` Eric Dumazet
2016-10-27 17:54 ` Thomas Falcon
2016-10-27 18:08 ` Eric Dumazet
2016-10-30 0:21 ` Jonathan Maxwell
2016-11-02 21:40 ` Brian King
2016-11-06 21:22 ` Jonathan Maxwell
2016-11-09 16:02 ` Brian King
2016-11-11 18:16 ` Brian King
2016-12-08 22:40 ` [PATCH] ibmveth: set correct gso_size and gso_type Thomas Falcon
2016-12-10 1:31 ` [PATCH net v2] " Thomas Falcon
2016-12-10 3:28 ` Eric Dumazet
2016-12-10 18:39 ` [PATCH net v3] " Thomas Falcon
2016-12-10 20:56 ` David Miller [this message]
2016-12-13 15:49 ` Thomas Falcon
2016-12-10 3:48 ` [PATCH] " David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161210.155647.1988856288960520451.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brking@linux.vnet.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=jmaxwell37@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pradeeps@linux.vnet.ibm.com \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=zdai@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).