MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] Squash to "selftests: bpf: add bpf_first test"
Date: Tue, 3 May 2022 18:17:28 -0700 (PDT)	[thread overview]
Message-ID: <d734f759-837f-3f14-cf86-757727661e7d@linux.intel.com> (raw)
In-Reply-To: <3efc49e473d2fbb03c9577aea5959b35d29d2c9e.1651625191.git.geliang.tang@suse.com>

On Wed, 4 May 2022, Geliang Tang wrote:

> Set scheduler to default after test.

Looks good to squash, thanks Geliang.

- Mat

>
> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> ---
> tools/testing/selftests/bpf/prog_tests/mptcp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/mptcp.c b/tools/testing/selftests/bpf/prog_tests/mptcp.c
> index 925858d63a9c..3106e013b9ca 100644
> --- a/tools/testing/selftests/bpf/prog_tests/mptcp.c
> +++ b/tools/testing/selftests/bpf/prog_tests/mptcp.c
> @@ -371,6 +371,7 @@ static void test_first(void)
>
> 	close(client_fd);
> 	close(server_fd);
> +	system("sysctl -qw net.mptcp.scheduler=default");
> 	bpf_link__destroy(link);
> 	mptcp_bpf_first__destroy(first_skel);
> }
> -- 
> 2.34.1
>
>
>

--
Mat Martineau
Intel

  reply	other threads:[~2022-05-04  1:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  0:47 [PATCH mptcp-next] Squash to "selftests: bpf: add bpf_first test" Geliang Tang
2022-05-04  1:17 ` Mat Martineau [this message]
2022-05-04  2:17 ` Squash to "selftests: bpf: add bpf_first test": Tests Results MPTCP CI
2022-05-04  7:03 ` [PATCH mptcp-next] Squash to "selftests: bpf: add bpf_first test" Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2022-05-07  6:17 [PATCH mptcp-next] Squash to "selftests: bpf: add MPTCP test base" Geliang Tang
2022-05-07  6:17 ` [PATCH mptcp-next] Squash to "selftests: bpf: add bpf_first test" Geliang Tang

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=d734f759-837f-3f14-cf86-757727661e7d@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=geliang.tang@suse.com \
    --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