From: Daniel Borkmann <dborkman@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, lw1a2.jing@gmail.com,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
David L Stevens <david.stevens@oracle.com>
Subject: Re: [PATCH net v4] ipv6: mld: fix add_grhead skb_over_panic for devs with large MTUs
Date: Wed, 05 Nov 2014 22:31:21 +0100 [thread overview]
Message-ID: <545A9729.8020308@redhat.com> (raw)
In-Reply-To: <1415220449.13896.15.camel@edumazet-glaptop2.roam.corp.google.com>
On 11/05/2014 09:47 PM, Eric Dumazet wrote:
...
> Thanks for your patience ;)
No problem, thanks for the feedback, Eric!
next prev parent reply other threads:[~2014-11-05 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 19:27 [PATCH net v4] ipv6: mld: fix add_grhead skb_over_panic for devs with large MTUs Daniel Borkmann
2014-11-05 20:47 ` Eric Dumazet
2014-11-05 21:31 ` Daniel Borkmann [this message]
2014-11-05 22:11 ` Cong Wang
2014-11-05 22:46 ` Daniel Borkmann
2014-11-05 23:32 ` Hannes Frederic Sowa
2014-11-06 3:14 ` 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=545A9729.8020308@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=david.stevens@oracle.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=lw1a2.jing@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).