From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH net-next v2 0/2] mptcp: add last time fields in mptcp_info
Date: Wed, 10 Apr 2024 14:01:03 -0700 [thread overview]
Message-ID: <20240410140103.37b94193@kernel.org> (raw)
In-Reply-To: <b8c14751-37a9-4a3d-b9af-a5c697d34781@kernel.org>
On Wed, 10 Apr 2024 21:31:13 +0200 (GMT+02:00) Matthieu Baerts wrote:
> > Hi Mat, is this causing skips in selftests by any chance?
> >
> > # 07 ....chk last_data_sent [SKIP] Feature probably not supported
> > # 08 ....chk last_data_recv [SKIP] Feature probably not supported
> > # 09 ....chk last_ack_recv [SKIP] Feature probably not supported
>
> Yes it does, I should have added a note about that, sorry: that's because
> SS needs to be patched as well to display the new counters.
>
> https://patchwork.kernel.org/project/mptcp/patch/fd9e850f1e00691204f1dfebc63c01c6a4318c10.1711705327.git.geliang@kernel.org/
>
> This patch will be sent when the kernel one will be accepted.
I see, applied locally now, thanks!
> Is it an issue? The modification of the selftests can be applied later
> if you prefer.
Not sure. If it doesn't happen super often maybe co-post the iproute2
patch as described:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#co-posting-changes-to-user-space-components
and I'll apply it on the worker machines manually.
> Earlier today, I was looking at changing NIPA not to mark the whole
> selftest as "SKIP" but I saw it was not a bug: a check is there to
> mark everything as skipped if one subtest is marked as skipped
> from what I understood. So I guess we don't want to change that :)
Correct :) It's working as intended :)
> > I'll "hide it" from patchwork for now..
> > --
> > pw-bot: defer
>
> Thank you! Do you prefer if I resend only patch 1/2 for now?
No need, restored the patches back, let's see if next run is clean.
next prev parent reply other threads:[~2024-04-10 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 9:48 [PATCH net-next v2 0/2] mptcp: add last time fields in mptcp_info Matthieu Baerts (NGI0)
2024-04-10 9:48 ` [PATCH net-next v2 1/2] " Matthieu Baerts (NGI0)
2024-04-10 9:48 ` [PATCH net-next v2 2/2] selftests: mptcp: test last time mptcp_info Matthieu Baerts (NGI0)
2024-04-10 18:34 ` [PATCH net-next v2 0/2] mptcp: add last time fields in mptcp_info Jakub Kicinski
2024-04-10 19:31 ` Matthieu Baerts
2024-04-10 21:01 ` Jakub Kicinski [this message]
2024-04-11 9:17 ` Matthieu Baerts
2024-04-11 17:30 ` patchwork-bot+netdevbpf
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=20240410140103.37b94193@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).