All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <martineau@kernel.org>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 0/9] Update scheduler refactor commits
Date: Wed, 16 Aug 2023 17:07:55 -0700 (PDT)	[thread overview]
Message-ID: <ecf0e1f7-feae-e8bb-dad0-5e3a87b4aec5@kernel.org> (raw)
In-Reply-To: <cover.1692080803.git.geliang.tang@suse.com>

On Tue, 15 Aug 2023, Geliang Tang wrote:

> Update scheduler refactor commits:
> - drop data_init interface.
> - call mptcp_sched_default_get_subflow in get_send/retrans.
> - update commit logs.
>

Thanks for the changes Geliang, these look good to squash.

Matthieu, I think the build failures were due to the squash commits being 
applied after the final export branch commit?

- Mat


> Geliang Tang (9):
>  Squash to "mptcp: add struct mptcp_sched_ops"
>  Squash to "mptcp: add scheduler wrappers"
>  Squash to "mptcp: register default scheduler"
>  Squash to "selftests/bpf: Add mptcp sched structs"
>  Squash to "selftests/bpf: Add bpf_first scheduler"
>  Squash to "selftests/bpf: Add bpf_bkup scheduler"
>  Squash to "selftests/bpf: Add bpf_rr scheduler"
>  Squash to "selftests/bpf: Add bpf_red scheduler"
>  Squash to "selftests/bpf: Add bpf_burst scheduler"
>
> include/net/mptcp.h                           |  4 +--
> net/mptcp/sched.c                             | 36 ++++---------------
> tools/testing/selftests/bpf/bpf_tcp_helpers.h |  4 +--
> .../selftests/bpf/progs/mptcp_bpf_bkup.c      | 11 ++----
> .../selftests/bpf/progs/mptcp_bpf_burst.c     | 15 +++-----
> .../selftests/bpf/progs/mptcp_bpf_first.c     | 10 ++----
> .../selftests/bpf/progs/mptcp_bpf_red.c       |  9 ++---
> .../selftests/bpf/progs/mptcp_bpf_rr.c        | 11 ++----
> 8 files changed, 23 insertions(+), 77 deletions(-)
>
> -- 
> 2.35.3
>
>
>

  parent reply	other threads:[~2023-08-17  0:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  6:29 [PATCH mptcp-next 0/9] Update scheduler refactor commits Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 1/9] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 2/9] Squash to "mptcp: add scheduler wrappers" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 3/9] Squash to "mptcp: register default scheduler" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 4/9] Squash to "selftests/bpf: Add mptcp sched structs" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 5/9] Squash to "selftests/bpf: Add bpf_first scheduler" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 6/9] Squash to "selftests/bpf: Add bpf_bkup scheduler" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 7/9] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 8/9] Squash to "selftests/bpf: Add bpf_red scheduler" Geliang Tang
2023-08-15  6:29 ` [PATCH mptcp-next 9/9] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-15  6:41   ` Squash to "selftests/bpf: Add bpf_burst scheduler": Build Failure MPTCP CI
2023-08-15  7:44   ` Squash to "selftests/bpf: Add bpf_burst scheduler": Tests Results MPTCP CI
2023-08-17  0:07 ` Mat Martineau [this message]
2023-08-17  9:30   ` [PATCH mptcp-next 0/9] Update scheduler refactor commits Matthieu Baerts

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=ecf0e1f7-feae-e8bb-dad0-5e3a87b4aec5@kernel.org \
    --to=martineau@kernel.org \
    --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 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.