From: David Miller <davem@davemloft.net>
To: berny156@gmx.de
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
ncardwell@google.com
Subject: Re: [PATCH] tcp_bbr: fix Kconfig to be able to make BBR the default congestion algorithm
Date: Wed, 30 Nov 2016 22:43:37 -0500 (EST) [thread overview]
Message-ID: <20161130.224337.1171980480771762847.davem@davemloft.net> (raw)
In-Reply-To: <b37e4220-b857-4853-f2e2-b77bb08115e5@gmx.de>
From: Bernhard Held <berny156@gmx.de>
Date: Wed, 30 Nov 2016 23:31:29 +0100
> Add missing line to be able to make BBR the default
> congestion algorithm.
>
> Signed-off-by: Bernhard Held <berny156@gmx.de>
The current tree already has this fix.
prev parent reply other threads:[~2016-12-01 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 22:31 [PATCH] tcp_bbr: fix Kconfig to be able to make BBR the default congestion algorithm Bernhard Held
2016-11-30 23:04 ` Eric Dumazet
2016-12-01 3:43 ` 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=20161130.224337.1171980480771762847.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=berny156@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.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).