From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] Checksum fixes
Date: Fri, 13 Jun 2014 13:27:01 -0700 (PDT) [thread overview]
Message-ID: <20140613.132701.1226816839536831499.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1406121554310.30089@tomh.mtv.corp.google.com>
From: Tom Herbert <therbert@google.com>
Date: Thu, 12 Jun 2014 16:02:52 -0700 (PDT)
> Fixes related to some recent checksum modifications.
>
> - Fix logic in saving checksums complete in __skb_checksum_complete
> - Call __skb_checksum_complete from UDP if we are checksumming over
> whole packet in order to save checksum.
> - Fixes to VXLAN to work correctly with checksum complete
I figure this series will need to be respun after you figure out the
problems Geert is still seeing with the full series applied.
prev parent reply other threads:[~2014-06-13 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 23:02 [PATCH 0/4] Checksum fixes Tom Herbert
2014-06-13 20:27 ` David Miller [this message]
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=20140613.132701.1226816839536831499.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).