From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: sync requests from bpf-next
Date: Wed, 10 Apr 2024 17:28:05 +0200 [thread overview]
Message-ID: <ec30c6c4-9bab-4884-bfa2-fa1fd6ca00ed@kernel.org> (raw)
In-Reply-To: <9f273947-14c9-47ef-b135-12571003f4bc@kernel.org>
On 10/04/2024 17:26, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 10/04/2024 12:21, Geliang Tang wrote:
>> These four patches need to be merged into mptcp_net-next from bpf-next
>> to avoid conflicts:
>
> For which series do you need these patches to be cherry-picked from
> bpf-next repo?
>
> I assume it is for "use start_server and connect_to helpers" and "export
> send_recv_data (v4)", right? These series don't directly modify MPTCP
> code or tests, do you need MPTCP CI to validate them?
I forgot to add that I manually applied these patches on top of the
bpf-next tree, and pushed a "patchew/" tag. So our CI will validate them
(even if I'm not sure the results will be very interesting).
> If you need tests to be performed by our CI, you can also push any new
> branches (a few are ignored, see ".github/workflows/tests.yml") on your
> fork repo on GitHub. I guess you can do the same with BPF repo [1] on
> GitHub.
>
> [1] https://github.com/kernel-patches/bpf
>
> Cheers,
> Matt
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-04-10 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 10:21 sync requests from bpf-next Geliang Tang
2024-04-10 15:26 ` Matthieu Baerts
2024-04-10 15:28 ` Matthieu Baerts [this message]
2024-04-12 1:21 ` Geliang Tang
2024-04-12 8:04 ` Matthieu Baerts
2024-04-15 1:47 ` 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=ec30c6c4-9bab-4884-bfa2-fa1fd6ca00ed@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).