From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
dsahern@kernel.org, willemb@google.com, netdev@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next 1/2] tcp: make SOF_TIMESTAMPING_RX_SOFTWARE feature per socket
Date: Tue, 27 Aug 2024 07:46:20 -0700 [thread overview]
Message-ID: <20240827074620.03f4d92a@kernel.org> (raw)
In-Reply-To: <20240825152440.93054-2-kerneljasonxing@gmail.com>
On Sun, 25 Aug 2024 23:24:39 +0800 Jason Xing wrote:
> However, there is one particular case that fails the selftests with
> "./rxtimestamp: Expected swtstamp to not be set." error printing in
> testcase 6.
In case you ever find yourself looking for ways to improve our tests
may I suggest trying to speed up fcnal_test.sh? That'd be a very
productive use of time.
next prev parent reply other threads:[~2024-08-27 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 15:24 [PATCH net-next 0/2] timestamp: control SOF_TIMESTAMPING_RX_SOFTWARE feature per socket Jason Xing
2024-08-25 15:24 ` [PATCH net-next 1/2] tcp: make " Jason Xing
2024-08-26 13:24 ` Willem de Bruijn
2024-08-26 13:40 ` Jason Xing
2024-08-26 16:03 ` Willem de Bruijn
2024-08-26 16:41 ` Jason Xing
2024-08-26 18:43 ` Willem de Bruijn
2024-08-26 23:42 ` Jason Xing
2024-08-27 13:20 ` Willem de Bruijn
2024-08-27 15:27 ` Jason Xing
2024-08-27 17:08 ` Willem de Bruijn
2024-08-28 0:43 ` Jason Xing
2024-08-28 13:44 ` Willem de Bruijn
2024-08-28 14:02 ` Jason Xing
2024-08-28 14:10 ` Willem de Bruijn
2024-08-28 14:18 ` Jason Xing
2024-08-27 14:46 ` Jakub Kicinski [this message]
2024-08-27 15:31 ` Jason Xing
2024-08-25 15:24 ` [PATCH net-next 2/2] net: " Jason Xing
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=20240827074620.03f4d92a@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
/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.