mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: linmiaohe <linmiaohe@huawei.com>
To: David Miller <davem@davemloft.net>, <willemb@google.com>,
	<fw@strlen.de>, <edumazet@google.com>, <pabeni@redhat.com>,
	<pctammela@gmail.com>, <deepa.kernel@gmail.com>,
	<sbrivio@redhat.com>, <mirq-linux@rere.qmqm.pl>,
	<linux-kernel@vger.kernel.org>
Cc: Mingfangsen <mingfangsen@huawei.com>
Subject: [PATCH net] trival: net: skbuff: fix comment in skbuff.h
Date: Wed, 3 Apr 2019 17:15:27 +0800	[thread overview]
Message-ID: <625895cf-f9aa-cb8b-effc-556f6ae70464@huawei.com> (raw)

From: Miaohe Lin <linmiaohe@huawei.com>

It should be IPv6|UDP instead of IPv4|UDP for NETIF_F_IPV6_CSUM

Signed-off-by: linmiaohe <linmiaohe@huawei.com>
---
 include/linux/skbuff.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 69b5538adcea..9683e00a5a79 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -71,7 +71,7 @@
  *     NETIF_F_IPV6_CSUM - Driver (device) is only able to checksum plain
  *                       TCP or UDP packets over IPv6. These are specifically
  *                       unencapsulated packets of the form IPv6|TCP or
- *                       IPv4|UDP where the Next Header field in the IPv6
+ *                       IPv6|UDP where the Next Header field in the IPv6
  *                       header is either TCP or UDP. IPv6 extension headers
  *                       are not supported with this feature. This feature
  *                       cannot be set in features for a device with
-- 
2.19.1



.



             reply	other threads:[~2019-04-03  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03  9:15 linmiaohe [this message]
2019-04-04  7:35 ` Mukesh Ojha

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=625895cf-f9aa-cb8b-effc-556f6ae70464@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=davem@davemloft.net \
    --cc=deepa.kernel@gmail.com \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingfangsen@huawei.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=pabeni@redhat.com \
    --cc=pctammela@gmail.com \
    --cc=sbrivio@redhat.com \
    --cc=willemb@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

all inboxes | Powered by JetHome®