From: Stephen Hemminger <stephen@networkplumber.org>
To: Christoph Paasch <cpaasch@apple.com>
Cc: netdev@vger.kernel.org, Yuchung Cheng <ycheng@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH iproute2] ip: add fastopen_no_cookie option to ip route
Date: Tue, 31 Oct 2017 22:20:27 +0100 [thread overview]
Message-ID: <20171031222027.5a3458dd@shemminger-XPS-13-9360> (raw)
In-Reply-To: <20171031193510.GE44287@da0602a-dhcp105.apple.com>
On Tue, 31 Oct 2017 12:35:10 -0700
Christoph Paasch <cpaasch@apple.com> wrote:
> Hello Stephen,
>
> On 27/10/17 - 08:40:03, Stephen Hemminger wrote:
> > On Thu, 26 Oct 2017 11:10:38 -0700
> > Christoph Paasch <cpaasch@apple.com> wrote:
> >
> > > This patch adds fastopen_no_cookie option to enable/disable TCP fastopen
> > > without a cookie on a per-route basis.
> > >
> > > Support in Linux was added with 71c02379c762 (tcp: Configure TFO without
> > > cookie per socket and/or per route).
> > >
> > > Cc: Stephen Hemminger <stephen@networkplumber.org>
> > > Signed-off-by: Christoph Paasch <cpaasch@apple.com>
> >
> > Applied, thanks Christoph.
>
> I see that this patch is not yet in your repo.
>
> With the recent changes that went in, it also won't apply cleanly.
>
> Do you want me to rebase & resubmit the patch?
>
>
> Christoph
Not sure where it got lost. Please resubmit against net-next branch
prev parent reply other threads:[~2017-10-31 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 18:10 [PATCH iproute2] ip: add fastopen_no_cookie option to ip route Christoph Paasch
2017-10-27 6:40 ` Stephen Hemminger
2017-10-31 19:35 ` Christoph Paasch
2017-10-31 21:20 ` Stephen Hemminger [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=20171031222027.5a3458dd@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=cpaasch@apple.com \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).