From: David Miller <davem@davemloft.net>
To: shanwei@cn.fujitsu.com
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi,
jmorris@namei.org, kaber@trash.net
Subject: Re: [PATCH] tcp: Remove debug macro of TCP_CHECK_TIMER
Date: Sun, 20 Feb 2011 11:10:40 -0800 (PST) [thread overview]
Message-ID: <20110220.111040.112609363.davem@davemloft.net> (raw)
In-Reply-To: <4D60C901.8050307@cn.fujitsu.com>
From: Shan Wei <shanwei@cn.fujitsu.com>
Date: Sun, 20 Feb 2011 15:55:45 +0800
>
> Now, TCP_CHECK_TIMER is not used for debuging, it does nothing.
> And, it has been there for several years, maybe 6 years.
>
> Remove it to keep code clearer.
>
> Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
Applied.
prev parent reply other threads:[~2011-02-20 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 7:55 [PATCH] tcp: Remove debug macro of TCP_CHECK_TIMER Shan Wei
2011-02-20 19:10 ` 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=20110220.111040.112609363.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=shanwei@cn.fujitsu.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).