From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/7] udp: Generic functions to set checksum
Date: Sun, 01 Jun 2014 19:49:42 -0700 (PDT) [thread overview]
Message-ID: <20140601.194942.1014308083943595457.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1405282113290.6331@tomh.mtv.corp.google.com>
From: Tom Herbert <therbert@google.com>
Date: Wed, 28 May 2014 21:23:27 -0700 (PDT)
> Added udp_set_csum and udp6_set_csum functions to set UDP checksums
> in packets. These are for simple UDP packets such as those that might
> be created in UDP tunnels.
>
> Signed-off-by: Tom Herbert <therbert@google.com>
> ---
> include/net/ip6_checksum.h | 45 +++++++++++++++++++++++++++++++++++++++++++++
> include/net/udp.h | 42 ++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 87 insertions(+)
>
> diff --git a/include/net/ip6_checksum.h b/include/net/ip6_checksum.h
> index 8ac5c21..7382a12 100644
> --- a/include/net/ip6_checksum.h
> +++ b/include/net/ip6_checksum.h
> @@ -82,5 +82,50 @@ static inline void tcp_v6_send_check(struct sock *sk, struct sk_buff *skb)
> }
> #endif
>
> +static inline __sum16 udp_v6_check(int len,
> + const struct in6_addr *saddr,
> + const struct in6_addr *daddr,
> + __wsum base)
Tom, please indent this correctly. I applied this patch and double checked
and it comes out like this:
static inline __sum16 udp_v6_check(int len,
const struct in6_addr *saddr,
const struct in6_addr *daddr,
__wsum base)
Those arguments must start precisely at the first column after the
openning parenthesis of the function declaration.
prev parent reply other threads:[~2014-06-02 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 4:23 [PATCH 1/7] udp: Generic functions to set checksum Tom Herbert
2014-06-02 2:49 ` 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=20140601.194942.1014308083943595457.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).