From: David Miller <davem@davemloft.net>
To: sarveshwar.bandi@emulex.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] bridge: Pull ip header into skb->data before looking into ip header.
Date: Wed, 10 Oct 2012 22:53:58 -0400 (EDT) [thread overview]
Message-ID: <20121010.225358.819989131525970516.davem@davemloft.net> (raw)
In-Reply-To: <6f6f2599-15e5-49a7-973c-d2c36483427d@CMEXHTCAS1.ad.emulex.com>
From: <sarveshwar.bandi@emulex.com>
Date: Wed, 10 Oct 2012 16:45:01 +0530
> From: Sarveshwar Bandi <sarveshwar.bandi@emulex.com>
>
> If lower layer driver leaves the ip header in the skb fragment, it needs to
> be first pulled into skb->data before inspecting ip header length or ip version
> number.
>
> Signed-off-by: Sarveshwar Bandi <sarveshwar.bandi@emulex.com>
Applied.
prev parent reply other threads:[~2012-10-11 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 11:15 [PATCH] bridge: Pull ip header into skb->data before looking into ip header sarveshwar.bandi
2012-10-11 2:53 ` 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=20121010.225358.819989131525970516.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sarveshwar.bandi@emulex.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).