kernelci / kernelci/kernelci-core

Add branch `export` and `export-net` from MPTCP tree

Open
#2,690 0 comments 0 reactions 1 assignee Claimed by @nuclearcat View on GitHub
Dominant language
Python
Stars
120
Forks
107
Avg merge
1d 2h
Merged PRs (30d)
21

Description

- **Which Git branch do you want to add?**

⇨ Git repo URL: https://github.com/multipath-tcp/mptcp_net-next.git

⇨ Git branch names: `export` and `export-net`

Note that these branches are overridden (rebased/re-written) each time they are modified. Is it an issue? If it is, `for-review` and `for-review-net` can be used instead, but they contain a lot of merge commits.

- **How much build coverage do you need for your branch?**

⇨ Build coverage choice: Something between 2 and 3: it doesn't need to include many architectures, but it would be nice to have builds covering 32 and 64-bit architectures ; and we need to have some builds with `CONFIG_MPTCP` enabled (not enabled by default in defconfig).

Note that we have KSelftests (`tools/testing/selftests/net/mptcp/`) and KUnit tests (`MPTCP_KUNIT_TEST`)

- **How often do you expect this branch to be updated?**

⇨ Estimated frequency: one or two times a day

- **Who should the email reports be sent to?**

⇨ Recipients: Is it possible to get emails only in case of problems? Can we start with my email address (`matttbe` at `kernel.org`), and change later if needed?

Thanks!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.