According to some bug reports we had in the past, setting the MPTCP
endpoints might be confusing, and the wrong flags might be set.

This series adds missing info for the 'dev' parameter in the manual, but
also clarify a few other parameters.

While at it, a better error message is reported when 'id 0' is used to
'add' or 'change' an endpoint.

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Matthieu Baerts (NGI0) (7):
      man: mptcp: document 'dev IFNAME'
      man: mptcp: clarify 'signal' and 'subflow' flags
      man: mptcp: 'port' has to be used with 'signal'
      man: mptcp: 'backup' flag also affects outgoing data
      man: mptcp: 'fullmesh' has to be used with 'subflow'
      man: mptcp: clarify the 'ID' parameter
      ip: mptcp: 'id 0' is only for 'del'

 ip/ipmptcp.c        |  2 ++
 man/man8/ip-mptcp.8 | 44 +++++++++++++++++++++++++++++++++++---------
 2 files changed, 37 insertions(+), 9 deletions(-)
---
base-commit: 3e807112fdf3d7b89a8295379dd8474f08a38b4b
change-id: 20240726-upstream-iproute2-net-20240726-mptcp-man-user-feedback-97612666993b

Best regards,
-- 
Matthieu Baerts (NGI0) <matttbe@kernel.org>