From: Geliang Tang <geliang@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] mptcp: remove unused returned value
Date: Wed, 10 Sep 2025 11:44:58 +0800 [thread overview]
Message-ID: <4b75974ccfc64501c417a75d697e630821fc02b1.camel@kernel.org> (raw)
In-Reply-To: <b46a064d54f6418fe1d61250921674510beb4652.camel@kernel.org>
Hi Matt,
On Wed, 2025-09-10 at 11:38 +0800, Geliang Tang wrote:
> Hi Matt,
>
> On Sat, 2025-09-06 at 16:13 +0200, Matthieu Baerts (NGI0) wrote:
> > When working on a fix modifying mptcp_check_data_fin(), I noticed
> > the
> > returned value was no longer used.
> >
> > It looks like it was used for 3 days, between commit 7ed90803a213
> > ("mptcp: send explicit ack on delayed ack_seq incr") and commit
> > ea4ca586b16f ("mptcp: refine MPTCP-level ack scheduling").
> >
> > This returned value can be safely removed.
> >
> > Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
> LGTM!
>
> Reviewed-by: Geliang Tang <geliang@kernel.org>
Please update the subject when applying this patch, similar to this:
mptcp: remove unused returned value of check_data_fin
Thanks,
-Geliang
>
> Thanks,
> -Geliang
>
> > ---
> > net/mptcp/protocol.c | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> > index
> > 1c26acf6c4145896ecbb5c7f7004121c66a20649..f3dda47ad1d70b5c6a326c17d
> > be
> > 6d244c5638ca2 100644
> > --- a/net/mptcp/protocol.c
> > +++ b/net/mptcp/protocol.c
> > @@ -530,11 +530,10 @@ static void mptcp_cleanup_rbuf(struct
> > mptcp_sock *msk, int copied)
> > }
> > }
> >
> > -static bool mptcp_check_data_fin(struct sock *sk)
> > +static void mptcp_check_data_fin(struct sock *sk)
> > {
> > struct mptcp_sock *msk = mptcp_sk(sk);
> > u64 rcv_data_fin_seq;
> > - bool ret = false;
> >
> > /* Need to ack a DATA_FIN received from a peer while this
> > side
> > * of the connection is in ESTABLISHED, FIN_WAIT1, or
> > FIN_WAIT2.
> > @@ -572,12 +571,10 @@ static bool mptcp_check_data_fin(struct sock
> > *sk)
> > break;
> > }
> >
> > - ret = true;
> > if (!__mptcp_check_fallback(msk))
> > mptcp_send_ack(msk);
> > mptcp_close_wake_up(sk);
> > }
> > - return ret;
> > }
> >
> > static void mptcp_dss_corruption(struct mptcp_sock *msk, struct
> > sock
> > *ssk)
> >
> > ---
> > base-commit: e9091ee333eb716a0933dcb08617228dcd3d3623
> > change-id: 20250906-check_data_fin_ret-6d284170880a
> >
> > Best regards,
next prev parent reply other threads:[~2025-09-10 3:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 14:13 [PATCH mptcp-next] mptcp: remove unused returned value Matthieu Baerts (NGI0)
2025-09-06 16:19 ` MPTCP CI
2025-09-10 3:38 ` Geliang Tang
2025-09-10 3:44 ` Geliang Tang [this message]
2025-09-10 9:07 ` Matthieu Baerts
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=4b75974ccfc64501c417a75d697e630821fc02b1.camel@kernel.org \
--to=geliang@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.