From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, gerrit@erg.abdn.ac.uk
Subject: Re: [PATCH net-next] dccp: consistently use dccp_write_space()
Date: Sun, 04 Jun 2017 19:58:52 -0400 (EDT) [thread overview]
Message-ID: <20170604.195852.727811399844205302.davem@davemloft.net> (raw)
In-Reply-To: <1496415746.5031.6.camel@edumazet-glaptop3.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 02 Jun 2017 08:02:26 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> DCCP uses dccp_write_space() for sk->sk_write_space method.
>
> Unfortunately a passive connection (as provided by accept())
> is using the generic sk_stream_write_space() function.
>
> Lets simply inherit sk->sk_write_space from the parent
> instead of forcing the generic one.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Applied, thanks Eric.
prev parent reply other threads:[~2017-06-04 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 15:02 [PATCH net-next] dccp: consistently use dccp_write_space() Eric Dumazet
2017-06-04 23:58 ` 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=20170604.195852.727811399844205302.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=gerrit@erg.abdn.ac.uk \
--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).