From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [Patch net] igb: pass the correct maxlen for eth_get_headlen()
Date: Fri, 24 Apr 2015 18:07:20 -0700 [thread overview]
Message-ID: <1429924040.2644.63.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1429724760-10075-1-git-send-email-xiyou.wangcong@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
On Wed, 2015-04-22 at 10:45 -0700, Cong Wang wrote:
> The second parameter of eth_get_headlen() is the length of
> the frame buffer, not the header length of skb.
>
> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
> ---
> drivers/net/ethernet/intel/igb/igb_main.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Dropping this patch based on feedback from Alex.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-04-25 1:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 17:45 [Patch net] igb: pass the correct maxlen for eth_get_headlen() Cong Wang
2015-04-22 17:45 ` [Patch net] fm10k: " Cong Wang
2015-04-22 17:45 ` [Patch net] ixgbe: " Cong Wang
2015-04-22 17:46 ` [Patch net] ixgbevf: " Cong Wang
2015-04-22 19:43 ` [Patch net] igb: " Alexander Duyck
2015-04-22 20:14 ` Cong Wang
2015-04-22 20:21 ` Alexander Duyck
2015-04-22 20:33 ` Cong Wang
2015-04-22 21:42 ` Alexander Duyck
2015-04-22 21:56 ` Cong Wang
2015-04-22 22:34 ` Alexander Duyck
2015-04-22 23:23 ` Cong Wang
2015-04-23 3:40 ` Alexander Duyck
2015-04-23 18:06 ` Cong Wang
2015-04-23 18:40 ` Alexander Duyck
2015-04-23 19:14 ` Cong Wang
2015-04-23 19:30 ` Cong Wang
2015-04-23 19:45 ` [Intel-wired-lan] " Alexander Duyck
2015-04-23 22:07 ` Cong Wang
2015-04-25 1:07 ` Jeff Kirsher [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=1429924040.2644.63.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@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).