From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Paasch <christoph.paasch@uclouvain.be>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: trivial: Remove nocache argument from tcp_v4_send_synack
Date: Sun, 18 Aug 2013 08:38:57 -0700 [thread overview]
Message-ID: <1376840337.21329.41.camel@edumazet-glaptop> (raw)
In-Reply-To: <1376840078-6556-1-git-send-email-christoph.paasch@uclouvain.be>
On Sun, 2013-08-18 at 17:34 +0200, Christoph Paasch wrote:
> The nocache-argument was used in tcp_v4_send_synack as an argument to
> inet_csk_route_req. However, since ba3f7f04ef2b (ipv4: Kill
> FLOWI_FLAG_RT_NOCACHE and associated code.) this is no more used.
>
> This patch removes the unsued argument from tcp_v4_send_synack.
>
> Signed-off-by: Christoph Paasch <christoph.paasch@uclouvain.be>
> ---
> net/ipv4/tcp_ipv4.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2013-08-18 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 15:34 [PATCH net-next] tcp: trivial: Remove nocache argument from tcp_v4_send_synack Christoph Paasch
2013-08-18 15:38 ` Eric Dumazet [this message]
2013-08-20 22:07 ` 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=1376840337.21329.41.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--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