From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: zheng.z.yan@intel.com, netdev@vger.kernel.org,
herbert@gondor.hengli.com.au
Subject: Re: [PATCH] gro: refetch inet6_protos[] after pulling ext headers
Date: Mon, 10 Oct 2011 14:26:40 -0400 (EDT) [thread overview]
Message-ID: <20111010.142640.1539695624934735900.davem@davemloft.net> (raw)
In-Reply-To: <1318152831.5276.30.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Sun, 09 Oct 2011 11:33:51 +0200
> Le dimanche 09 octobre 2011 à 16:34 +0800, Yan, Zheng a écrit :
>> ipv6_gro_receive() doesn't update the protocol ops after pulling
>> the ext headers. It looks like a typo.
>>
>> Signed-off-by: Zheng Yan <zheng.z.yan@intel.com>
...
>
> Good catch !
>
> Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
Applied, thanks!
prev parent reply other threads:[~2011-10-10 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 8:34 [PATCH] gro: refetch inet6_protos[] after pulling ext headers Yan, Zheng
2011-10-09 9:33 ` Eric Dumazet
2011-10-10 18:26 ` 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=20111010.142640.1539695624934735900.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.hengli.com.au \
--cc=netdev@vger.kernel.org \
--cc=zheng.z.yan@intel.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).