All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v11 0/8] add helpers and vars in mptcp_lib.sh, part 3
Date: Mon, 4 Mar 2024 13:31:47 +0100	[thread overview]
Message-ID: <8895ca8d-a13a-412f-a014-42abfe1ed1c7@kernel.org> (raw)
In-Reply-To: <cover.1709466624.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 03/03/2024 12:52, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> v11:
>  - fix the shellcheck error in v10
> 
> v10:
>  - split two more patches (#4 and #5) from #6 and #7
>  - update commit logs
> 
> v9:
>  - move print_larger_title from patch 5 to patch 2
>  - move MPTCP_LIB_TEST_FORMAT to a more suitable location in patch 4 and
>    patch 5
> 
> v8:
>  - address every comment from Matt in v7.

If you don't mind, please add a short changelog per individual patch.
Without that, it is quite hard to understand what you modified, if there
was something you didn't do on purpose or by accident, which patch has
moved where, etc. Without that, I end up re-reviewing the whole series
like it was a new one.

Apart from that, I think we are almost there. Two details on the two
first patches, then it looks like we might print 'OK', then 'FAIL' in
patch 4. And we might print 'OK', then some 'WARN' without '\n' at the
end in patch 8.


One important question: did you check the output when you force issues?
Just to make sure they are presented correctly, and mainly if we still
catch them!

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.

      parent reply	other threads:[~2024-03-04 12:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03 11:52 [PATCH mptcp-next v11 0/8] add helpers and vars in mptcp_lib.sh, part 3 Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 1/8] selftests: mptcp: print all error messages to stdout Geliang Tang
2024-03-04 12:31   ` Matthieu Baerts
2024-03-03 11:52 ` [PATCH mptcp-next v11 2/8] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-03-04 12:31   ` Matthieu Baerts
2024-03-03 11:52 ` [PATCH mptcp-next v11 3/8] selftests: mptcp: connect: fix misaligned output Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 4/8] selftests: mptcp: sockopt: print every test result Geliang Tang
2024-03-04 12:32   ` Matthieu Baerts
2024-03-03 11:52 ` [PATCH mptcp-next v11 5/8] selftests: mptcp: export TEST_COUNTER variable Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 6/8] selftests: mptcp: add print_title in mptcp_lib Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 7/8] selftests: mptcp: print test results with counters Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 8/8] selftests: mptcp: print test results with colors Geliang Tang
2024-03-03 12:40   ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-03-03 13:00   ` MPTCP CI
2024-03-04 12:32   ` [PATCH mptcp-next v11 8/8] selftests: mptcp: print test results with colors Matthieu Baerts
2024-03-04 12:31 ` Matthieu Baerts [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=8895ca8d-a13a-412f-a014-42abfe1ed1c7@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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.