From: Neal Cardwell <ncardwell@google.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Netdev <netdev@vger.kernel.org>,
Yuchung Cheng <ycheng@google.com>,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [PATCH net-next] tcp_westwood: fix tcp_westwood_info()
Date: Wed, 29 Apr 2015 19:36:27 -0400 [thread overview]
Message-ID: <CADVnQynFp3XXCnt6K7tTMHrA+tEHe7Z4ujnkaJ_jbzrPokzJtQ@mail.gmail.com> (raw)
In-Reply-To: <1430349658.3711.71.camel@edumazet-glaptop2.roam.corp.google.com>
On Wed, Apr 29, 2015 at 7:20 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> I forgot to update tcp_westwood when changing get_info() behavior,
> this patch should fix this.
>
> Fixes: 64f40ff5bbdb ("tcp: prepare CC get_info() access from getsockopt()")
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Acked-by: Neal Cardwell <ncardwell@google.com>
neal
next prev parent reply other threads:[~2015-04-29 23:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 23:23 [PATCH net-next 0/2] tcp: extend access to CC information Eric Dumazet
2015-04-28 23:23 ` [PATCH net-next 1/2] tcp: prepare CC get_info() access from getsockopt() Eric Dumazet
2015-04-29 0:58 ` Neal Cardwell
2015-04-29 7:55 ` Daniel Borkmann
2015-04-29 16:10 ` Yuchung Cheng
2015-04-29 22:12 ` David Miller
2015-04-29 22:40 ` Eric Dumazet
2015-04-29 23:20 ` [PATCH net-next] tcp_westwood: fix tcp_westwood_info() Eric Dumazet
2015-04-29 23:36 ` Neal Cardwell [this message]
2015-04-30 4:28 ` David Miller
2015-04-28 23:23 ` [PATCH net-next 2/2] tcp: add TCP_CC_INFO socket option Eric Dumazet
2015-04-29 1:00 ` Neal Cardwell
2015-04-29 8:17 ` Daniel Borkmann
2015-04-29 11:07 ` Eric Dumazet
2015-04-29 11:15 ` Daniel Borkmann
2015-04-29 16:15 ` Yuchung Cheng
2015-04-29 22:12 ` 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=CADVnQynFp3XXCnt6K7tTMHrA+tEHe7Z4ujnkaJ_jbzrPokzJtQ@mail.gmail.com \
--to=ncardwell@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=fengguang.wu@intel.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).