From: Ying Xue <ying.xue@windriver.com>
To: Zhaolong Zhang <zhangzl2013@126.com>, <jon.maloy@ericsson.com>,
<davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <tipc-discussion@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tipc: remove dead code in struct tipc_topsrv
Date: Thu, 24 Jan 2019 10:40:18 +0800 [thread overview]
Message-ID: <b419877d-49cb-15c6-7546-7b23a30631e3@windriver.com> (raw)
In-Reply-To: <1548295601-23063-1-git-send-email-zhangzl2013@126.com>
On 1/24/19 10:06 AM, Zhaolong Zhang wrote:
> max_rcvbuf_size is no longer used since commit "414574a0af36".
>
> Signed-off-by: Zhaolong Zhang <zhangzl2013@126.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
> ---
> net/tipc/topsrv.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/net/tipc/topsrv.c b/net/tipc/topsrv.c
> index efb16f6..4b1c083 100644
> --- a/net/tipc/topsrv.c
> +++ b/net/tipc/topsrv.c
> @@ -60,7 +60,6 @@
> * @awork: accept work item
> * @rcv_wq: receive workqueue
> * @send_wq: send workqueue
> - * @max_rcvbuf_size: maximum permitted receive message length
> * @listener: topsrv listener socket
> * @name: server name
> */
> @@ -72,7 +71,6 @@ struct tipc_topsrv {
> struct work_struct awork;
> struct workqueue_struct *rcv_wq;
> struct workqueue_struct *send_wq;
> - int max_rcvbuf_size;
> struct socket *listener;
> char name[TIPC_SERVER_NAME_LEN];
> };
> @@ -648,7 +646,6 @@ int tipc_topsrv_start(struct net *net)
> return -ENOMEM;
>
> srv->net = net;
> - srv->max_rcvbuf_size = sizeof(struct tipc_subscr);
> INIT_WORK(&srv->awork, tipc_topsrv_accept);
>
> strscpy(srv->name, name, sizeof(srv->name));
>
next prev parent reply other threads:[~2019-01-24 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 2:06 Zhaolong Zhang
2019-01-24 2:40 ` Ying Xue [this message]
2019-01-25 6:31 ` 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=b419877d-49cb-15c6-7546-7b23a30631e3@windriver.com \
--to=ying.xue@windriver.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=zhangzl2013@126.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
all inboxes | Powered by JetHome®