From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Cc: kernel test robot <yujie.liu@intel.com>
Subject: Re: [PATCH mptcp-next] Squash to "selftests/bpf: Add bpf_burst scheduler"
Date: Mon, 27 Nov 2023 18:56:10 +0100 [thread overview]
Message-ID: <7d1dfb5d-d82b-4320-8934-a44eb04a7434@kernel.org> (raw)
In-Reply-To: <14a1120c9bc792ead2b926208ce85b5f10cb99fd.1700624540.git.geliang.tang@suse.com>
Hi Geliang,
On 22/11/2023 04:42, Geliang Tang wrote:
> Fix the bpf selftests build error:
>
> progs/mptcp_bpf_burst.c:37:18: error: no member named 'write_seq' in 'struct tcp_sock'
> return tp ? tp->write_seq == tp->snd_nxt : true;
> ~~ ^
> 1 error generated.
> make: *** [Makefile:614: tools/testing/selftests/bpf/mptcp_bpf_burst.bpf.o] Error 1
> make: *** Waiting for unfinished jobs....
Thank you for the patch, now in our tree:
New patches for t/upstream:
- bd37dad396df: "squashed" in "selftests/bpf: Add bpf_burst scheduler"
- Results: d4787f01696d..1ee636354037 (export)
Tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20231127T175348
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2023-11-27 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 3:42 [PATCH mptcp-next] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-11-22 4:49 ` Squash to "selftests/bpf: Add bpf_burst scheduler": Tests Results MPTCP CI
2023-11-27 17:56 ` 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=7d1dfb5d-d82b-4320-8934-a44eb04a7434@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
--cc=yujie.liu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox