All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v4 mptcp-next 0/3] mptcp: more self-tests improvements
Date: Mon, 14 Feb 2022 16:38:54 +0100	[thread overview]
Message-ID: <cover.1644852970.git.pabeni@redhat.com> (raw)

This iteration tries to address the feedback from Mat on v3.

patch 1/3 is a somewhat related cleanup (to be squashed into existing
patch)
patch 2/3 should address the self-test failure
patch 3/3 avoids RFC breakage reported into the previous iteration,
leveraging the previois one

Patch 2/3 would probably deserve some additional self-tests. My plan is
to add them after that the existing ones are stable enough.

Paolo Abeni (3):
  Squash-to: "mptcp: constify a bunch of helpers"
  mptcp: more careful RM_ADDR generation
  mptcp: strict local address ID selection.

 include/uapi/linux/mptcp.h |  1 +
 net/mptcp/pm_netlink.c     | 59 ++++++++++++++++++---------------
 net/mptcp/protocol.c       |  3 ++
 net/mptcp/protocol.h       |  3 +-
 net/mptcp/subflow.c        | 67 +++++++++++++++++++++++++++++++++-----
 5 files changed, 97 insertions(+), 36 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-02-14 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 15:38 Paolo Abeni [this message]
2022-02-14 15:38 ` [PATCH v4 mptcp-next 1/3] Squash-to: "mptcp: constify a bunch of helpers" Paolo Abeni
2022-02-15  9:48   ` Matthieu Baerts
2022-02-14 15:38 ` [PATCH v4 mptcp-next 2/3] mptcp: more careful RM_ADDR generation Paolo Abeni
2022-02-14 18:41   ` Paolo Abeni
2022-02-15  1:19     ` Mat Martineau
2022-02-15 17:07       ` Paolo Abeni
2022-02-15 19:15         ` Mat Martineau
2022-02-16 18:38           ` Paolo Abeni
2022-02-16 23:48             ` Mat Martineau
2022-02-14 15:38 ` [PATCH v4 mptcp-next 3/3] mptcp: strict local address ID selection Paolo Abeni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1644852970.git.pabeni@redhat.com \
    --to=pabeni@redhat.com \
    --cc=mptcp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.