From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: generalize MAX_TCP_HEADER usage
Date: Sat, 29 Mar 2014 17:56:54 -0400 (EDT) [thread overview]
Message-ID: <20140329.175654.1000726174039601620.davem@davemloft.net> (raw)
In-Reply-To: <1395951546.12610.317.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 27 Mar 2014 13:19:06 -0700
> (Note that sk_stream_alloc_skb() uses MAX_TCP_HEADER anyway...)
But only after your changes.
Please make this clear in the commit message, I had to go check to see
if there were in fact MAX_TCP_HEADER uses in sk_stream_alloc_skb in
the current tree.
next prev parent reply other threads:[~2014-03-29 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 20:19 [PATCH net-next] tcp: generalize MAX_TCP_HEADER usage Eric Dumazet
2014-03-29 21:56 ` David Miller [this message]
2014-03-29 22:47 ` Eric Dumazet
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=20140329.175654.1000726174039601620.davem@davemloft.net \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.