From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: mptcp@lists.linux.dev
Cc: Matthieu Baerts <matthieu.baerts@tessares.net>,
Abaci Robot <abaci@linux.alibaba.com>,
Mat Martineau <martineau@kernel.org>,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Subject: [PATCH mptcp-next 0/3] mptcp: misc. small cleanups
Date: Wed, 29 Mar 2023 15:17:55 +0200 [thread overview]
Message-ID: <20230329-mptcp-misc-cleanups-v1-0-a839001f0b05@tessares.net> (raw)
Here is a series of small unrelated cleanups, nothing very important nor
big.
I don't know if the modification of the MAINTAINERS file should go in
-net instead.
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
---
Matthieu Baerts (3):
MAINTAINERS: add git trees for MPTCP
mptcp: remove unused 'remaining' variable
selftests: mptcp: remove duplicated entries in usage
MAINTAINERS | 2 ++
net/mptcp/options.c | 7 ++-----
tools/testing/selftests/net/mptcp/mptcp_connect.c | 8 ++++----
3 files changed, 8 insertions(+), 9 deletions(-)
---
base-commit: b2c5489c86ee1881dae3bc431ff6f284eb74f7ef
change-id: 20230329-mptcp-misc-cleanups-90754eb81610
Best regards,
--
Matthieu Baerts <matthieu.baerts@tessares.net>
next reply other threads:[~2023-03-29 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:17 Matthieu Baerts [this message]
2023-03-29 13:17 ` [PATCH mptcp-next 1/3] MAINTAINERS: add git trees for MPTCP Matthieu Baerts
2023-03-29 13:17 ` [PATCH mptcp-next 2/3] mptcp: remove unused 'remaining' variable Matthieu Baerts
2023-03-29 13:17 ` [PATCH mptcp-next 3/3] selftests: mptcp: remove duplicated entries in usage Matthieu Baerts
2023-03-29 14:34 ` selftests: mptcp: remove duplicated entries in usage: Tests Results MPTCP CI
2023-04-07 14:16 ` MPTCP CI
2023-04-07 13:25 ` [PATCH mptcp-next 0/3] mptcp: misc. small cleanups Paolo Abeni
2023-04-11 15:18 ` 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=20230329-mptcp-misc-cleanups-v1-0-a839001f0b05@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=abaci@linux.alibaba.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=martineau@kernel.org \
--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.