diff options
| author |   Matthieu Baerts (NGI0) <matttbe@kernel.org> | 2025-03-07 12:21:54 +0100 |
|---|---|---|
| committer |   Jakub Kicinski <kuba@kernel.org> | 2025-03-10 13:35:49 -0700 |
| commit | a49eb8ae95b8ce24f30a027f286baf8cac08a0ae (patch) | |
| tree | b2726136e8d300f8bb5a68cd27f4b45580afd77f /scripts/generate_rust_analyzer.py | |
| parent | mptcp: pm: avoid calling PM specific code from core (diff) | |
| download | linux-rng-a49eb8ae95b8ce24f30a027f286baf8cac08a0ae.tar.xz linux-rng-a49eb8ae95b8ce24f30a027f286baf8cac08a0ae.zip | |
mptcp: pm: worker: split in-kernel and common tasks
To make it clear what actions are in-kernel PM specific and which ones
are not and done for all PMs, e.g. sending ADD_ADDR and close associated
subflows when a RM_ADDR is received.
The behavioural is changed a bit: MPTCP_PM_ADD_ADDR_RECEIVED is now
treated after MPTCP_PM_ADD_ADDR_SEND_ACK and MPTCP_PM_RM_ADDR_RECEIVED,
but that should not change anything in practice.
Reviewed-by: Geliang Tang <geliang@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Link: https://patch.msgid.link/20250307-net-next-mptcp-pm-reorg-v1-10-abef20ada03b@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions