Patchwork

We use patchwork to manage the different patches sent on the mailing list: https://patchwork.kernel.org/project/mptcp/

Status

Patches for our tree

These status are set for patches that have to land in our tree first. These are specific to MPTCP. Once applied, MPTCP maintainers -- usually Mat -- will send them to netdev ML.

• New → Waiting for reviews from anybody (or status needs to be updated)
• Under review → In review by one of our team members or waiting for clarification
• Accepted → Applied in our tree
• Rejected → Related to MPTCP but this patch was not going in the right direction
• RFC → RFC, more to park this for later
• Changes requested → We need a new version
• Awaiting Upstream → Accepted but it is not for our tree, e.g. for iproute2 (we currently don't maintain a repo for it)
• Superseded → Replaced by a new version
• Queued → Waiting to be applied in our tree
• Needs ACK → Waiting for reviews for a "long time" (at least since the last weekly meeting) by members of our teams or someone else has to review it

Patches for other trees

Some patches are sent for inclusion in another tree but MPTCP ML is in CC. Typically, once accepted in our tree, patches are sent to netdev and our ML is in CC.

• Handled Elsewhere → Handled by others, typically netdev maintainers (best to check the exact status elsewhere)
• Mainlined → Handled by others and applied in another tree (if we don't forget to change the status)
• Not applicable → Not related to MPTCP, e.g. patches sent to netdev and our ML is in CC just for one patch: the others patches are then Not applicable

Archive

We archive some patches (applied, rejected, replaced and for other trees) after each weekly meeting to be able to discuss about what has recently been changed.