All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next 0/4] BPF packet scheduler updates part 3
Date: Mon, 31 Jul 2023 19:03:14 +0800	[thread overview]
Message-ID: <cover.1690801329.git.geliang.tang@suse.com> (raw)

Some cleanups.

Geliang Tang (4):
  Squash to "mptcp: add sched_data helpers"
  Squash to "bpf: Add bpf_mptcp_sched_kfunc_set"
  Squash to "selftests/bpf: add two mptcp netns helpers"
  Squash to "bpf: Export more bpf_burst related functions"

 net/mptcp/bpf.c                                | 10 ++++++++--
 net/mptcp/protocol.h                           |  6 ------
 net/mptcp/sched.c                              |  6 ++++++
 tools/testing/selftests/bpf/prog_tests/mptcp.c |  1 -
 4 files changed, 14 insertions(+), 9 deletions(-)

-- 
2.35.3


             reply	other threads:[~2023-07-31 11:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 11:03 Geliang Tang [this message]
2023-07-31 11:03 ` [PATCH mptcp-next 1/4] Squash to "mptcp: add sched_data helpers" Geliang Tang
2023-07-31 11:03 ` [PATCH mptcp-next 2/4] Squash to "bpf: Add bpf_mptcp_sched_kfunc_set" Geliang Tang
2023-07-31 11:03 ` [PATCH mptcp-next 3/4] Squash to "selftests/bpf: add two mptcp netns helpers" Geliang Tang
2023-07-31 11:03 ` [PATCH mptcp-next 4/4] Squash to "bpf: Export more bpf_burst related functions" Geliang Tang
2023-07-31 11:24   ` Squash to "bpf: Export more bpf_burst related functions": Build Failure MPTCP CI
2023-07-31 12:18   ` Squash to "bpf: Export more bpf_burst related functions": Tests Results MPTCP CI

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=cover.1690801329.git.geliang.tang@suse.com \
    --to=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.