From: Geliang Tang <geliang@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 09/11] selftests: mptcp: join: avoid declaring i if not used
Date: Sun, 28 Dec 2025 10:51:10 +0800 [thread overview]
Message-ID: <d16b1a026c14795fe02aaec2a4694ca6dbbb4360.camel@kernel.org> (raw)
In-Reply-To: <20251226-mptcp-issue-603-v1-9-bb30e331b839@kernel.org>
On Fri, 2025-12-26 at 07:40 +0100, Matthieu Baerts (NGI0) wrote:
> A few loops were declaring 'i', but this variable was not used.
>
> To avoid confusions, use '_' instead: it is more explicit to mark
> that
> this variable is not needed.
>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Reviewed-by: Geliang Tang <geliang@kernel.org>
Thanks,
-Geliang
> ---
> tools/testing/selftests/net/mptcp/mptcp_join.sh | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index 80e03168b419..4ca4bdfea246 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> @@ -603,8 +603,7 @@ wait_rm_addr()
> local old_cnt="${2}"
> local cnt
>
> - local i
> - for i in $(seq 10); do
> + for _ in $(seq 10); do
> cnt=$(rm_addr_count ${ns})
> [ "$cnt" = "${old_cnt}" ] || break
> sleep 0.1
> @@ -623,8 +622,7 @@ wait_rm_sf()
> local old_cnt="${2}"
> local cnt
>
> - local i
> - for i in $(seq 10); do
> + for _ in $(seq 10); do
> cnt=$(rm_sf_count ${ns})
> [ "$cnt" = "${old_cnt}" ] || break
> sleep 0.1
> @@ -648,8 +646,7 @@ wait_ll_ready()
> {
> local ns="${1}"
>
> - local i
> - for i in $(seq 50); do
> + for _ in $(seq 50); do
> ip -n "${ns}" -6 addr show scope link | grep "inet6
> fe80" |
> grep -qw "tentative" || break
> sleep 0.1
next prev parent reply other threads:[~2025-12-28 2:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 6:40 [PATCH mptcp-next 00/11] mptcp: avoid dup events + error + misc Matthieu Baerts (NGI0)
2025-12-26 6:40 ` [PATCH mptcp-next 01/11] mptcp: avoid dup SUB_CLOSED events after disconnect Matthieu Baerts (NGI0)
2026-01-04 3:15 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 02/11] selftests: mptcp: check no dup close events after error Matthieu Baerts (NGI0)
2026-01-04 3:17 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 03/11] mptcp: only reset subflow errors when propagated Matthieu Baerts (NGI0)
2026-01-04 3:30 ` Geliang Tang
2026-01-04 4:00 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 04/11] selftests: mptcp: check subflow errors in close events Matthieu Baerts (NGI0)
2025-12-26 6:40 ` [PATCH mptcp-next 05/11] selftests: mptcp: join: wait for estab event instead of MPJ Matthieu Baerts (NGI0)
2025-12-28 2:41 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 06/11] selftests: mptcp: join: fix wait_mpj helper Matthieu Baerts (NGI0)
2025-12-26 6:40 ` [PATCH mptcp-next 07/11] selftests: mptcp: join: userspace: wait for new events Matthieu Baerts (NGI0)
2025-12-28 2:48 ` Geliang Tang
2026-01-26 18:59 ` Matthieu Baerts
2025-12-26 6:40 ` [PATCH mptcp-next 08/11] selftests: mptcp: join chk_stale_nr: avoid dup stats Matthieu Baerts (NGI0)
2025-12-28 2:25 ` Geliang Tang
2025-12-28 4:43 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 09/11] selftests: mptcp: join: avoid declaring i if not used Matthieu Baerts (NGI0)
2025-12-28 2:51 ` Geliang Tang [this message]
2025-12-26 6:40 ` [PATCH mptcp-next 10/11] selftests: mptcp: connect: fix maybe-uninitialize warn Matthieu Baerts (NGI0)
2025-12-28 2:54 ` Geliang Tang
2026-01-26 19:02 ` Matthieu Baerts
2025-12-26 6:40 ` [PATCH mptcp-next 11/11] selftests: mptcp: connect cleanup TFO setup Matthieu Baerts (NGI0)
2025-12-28 2:59 ` Geliang Tang
2025-12-26 7:51 ` [PATCH mptcp-next 00/11] mptcp: avoid dup events + error + misc MPTCP CI
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=d16b1a026c14795fe02aaec2a4694ca6dbbb4360.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox