All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev, Yonglong Li <liyonglong@chinatelecom.cn>
Subject: Re: [PATCH mptcp-next 0/3] Squash to "selftests: mptcp: add a test case for MSG_PEEK"
Date: Mon, 19 Apr 2021 15:28:46 -0700 (PDT)	[thread overview]
Message-ID: <313ddde-a5d4-2c27-3b7-edc1e6751d38@linux.intel.com> (raw)
In-Reply-To: <20210419203355.3937162-1-matthieu.baerts@tessares.net>

On Mon, 19 Apr 2021, Matthieu Baerts wrote:

> I started this because I prefer avoiding setting a global variable before
> calling a function and reset it later in order to take a specific path in the
> called function. While at it, I also reduced duplicated code.
>
> But good thing, I also fixed two unwanted behaviours, see patches 1/3 and 2/3.
>
> Matthieu Baerts (3):
>  selftests: mptcp: use 2 different 'peek' modes
>  selftests: mptcp: same NS for Peek tests in IPv6
>  selftests: mptcp: avoid non-const global variables
>
> .../selftests/net/mptcp/mptcp_connect.sh      | 44 +++++++++----------
> 1 file changed, 22 insertions(+), 22 deletions(-)
>
> -- 
> 2.30.2

Hi Matthieu -

These look good to squash, thanks for the fixups!


--
Mat Martineau
Intel

  parent reply	other threads:[~2021-04-19 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 20:33 [PATCH mptcp-next 0/3] Squash to "selftests: mptcp: add a test case for MSG_PEEK" Matthieu Baerts
2021-04-19 20:33 ` [PATCH mptcp-next 1/3] selftests: mptcp: use 2 different 'peek' modes Matthieu Baerts
2021-04-19 20:33 ` [PATCH mptcp-next 2/3] selftests: mptcp: same NS for Peek tests in IPv6 Matthieu Baerts
2021-04-19 20:33 ` [PATCH mptcp-next 3/3] selftests: mptcp: avoid non-const global variables Matthieu Baerts
2021-04-19 22:28 ` Mat Martineau [this message]
2021-04-20  7:48   ` [PATCH mptcp-next 0/3] Squash to "selftests: mptcp: add a test case for MSG_PEEK" Matthieu Baerts

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=313ddde-a5d4-2c27-3b7-edc1e6751d38@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=liyonglong@chinatelecom.cn \
    --cc=matthieu.baerts@tessares.net \
    --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.