Patchwork

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

Status

New → Waiting for reviews from anybody
Under review → In review or waiting for precisions
Accepted → Applied in our tree
Rejected → We don't want that
RFC → RFC, more to park this for later
Not applicable → Not related to MPTCP, e.g. patches sent to net-next and our ML is CC just for one patch
Changes requested → We need a new version
Awaiting Upstream → A patch that is not for our tree, e.g. for iproute2
Superseded → Replaced by a new version
Deferred → 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)
Queued → Waiting to be applied in our tree
Needs ACK → Waiting for reviews a "long time" (at least since the last weekly meeting) or for someone specific