From: "Bjørn Mork" <bjorn@mork.no>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: remove useless check in napi_gro_frags()
Date: Thu, 19 Nov 2015 21:20:05 +0100 [thread overview]
Message-ID: <87oaepzqq2.fsf@nemi.mork.no> (raw)
In-Reply-To: <1447964139.22599.246.camel@edumazet-glaptop2.roam.corp.google.com> (Eric Dumazet's message of "Thu, 19 Nov 2015 12:15:39 -0800")
Eric Dumazet <eric.dumazet@gmail.com> writes:
> How many times should we crash before napi_frags_skb() returns NULL ?
..
> return NULL;
Huh? Now I'm lost here, too.
Bjørn
next prev parent reply other threads:[~2015-11-19 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 19:42 [PATCH net-next] net: remove useless check in napi_gro_frags() Eric Dumazet
2015-11-19 19:54 ` Alexei Starovoitov
2015-11-19 20:15 ` Eric Dumazet
2015-11-19 20:20 ` Bjørn Mork [this message]
2015-11-19 20:33 ` Eric Dumazet
2015-11-19 21:06 ` Aaron Conole
2015-11-19 21:43 ` Eric Dumazet
2015-11-20 19:59 ` David Miller
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=87oaepzqq2.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).