From: David Miller <davem@davemloft.net>
To: weiyj.lk@gmail.com
Cc: haiyangz@microsoft.com, kys@microsoft.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net/hyperv: rx_bytes should account the ether header size
Date: Wed, 01 Feb 2012 14:30:10 -0500 (EST) [thread overview]
Message-ID: <20120201.143010.1818830777509458347.davem@davemloft.net> (raw)
In-Reply-To: <CAPgLHd8M7vPra_gTH5J1RmR4nmSeuDEGCjghatd1BsOJEeGKKA@mail.gmail.com>
From: Wei Yongjun <weiyj.lk@gmail.com>
Date: Mon, 30 Jan 2012 16:14:02 +0800
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> skb->len after call eth_type_trans() does not include the ether
> header size, but rx_bytes should account it.
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Applied.
prev parent reply other threads:[~2012-02-01 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 8:14 [PATCH] net/hyperv: rx_bytes should account the ether header size Wei Yongjun
2012-02-01 19:30 ` 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=20120201.143010.1818830777509458347.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=weiyj.lk@gmail.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).