[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170116.135257.361979191382843875.davem@davemloft.net>
Date: Mon, 16 Jan 2017 13:52:57 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: marcelo.leitner@...il.com
Cc: netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
vyasevich@...il.com, nhorman@...driver.com
Subject: Re: [PATCH net-next] sctp: remove useless code from
sctp_apply_peer_addr_params
From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Date: Fri, 13 Jan 2017 18:31:15 -0200
> sctp_frag_point() doesn't store anything, and thus just calling it
> cannot do anything useful.
>
> sctp_apply_peer_addr_params is only called by
> sctp_setsockopt_peer_addr_params. When operating on an asoc,
> sctp_setsockopt_peer_addr_params will call sctp_apply_peer_addr_params
> once for the asoc, and then once for each transport this asoc has,
> meaning that the frag_point will be recomputed when updating the
> transports and calling it when updating the asoc is not necessary.
> IOW, no action is needed here and we can remove this call.
>
> Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Applied, but please put "[PATCH net-next v2]" or some other indication
in your Subject line so that new revisions of a patch are easily
discernable.
Thanks.
Powered by blists - more mailing lists