From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@linux.dev>,
Mat Martineau <martineau@kernel.org>
Subject: Re: [PATCH mptcp-net] MAINTAINERS: add Geliang as reviewer for MPTCP
Date: Tue, 19 Dec 2023 13:28:15 +0100 [thread overview]
Message-ID: <3cacaa5d-3951-4bbf-a7df-070021903510@kernel.org> (raw)
In-Reply-To: <20231215-mptcp-reviewers-geliang-v1-1-3fec5a0f8eac@kernel.org>
Hi Geliang, Mat,
On 15/12/2023 15:45, Matthieu Baerts wrote:
> For a long time now, Geliang has contributed to a lot of code and
> reviews related to MPTCP. So let's reflect that in the MAINTAINERS file.
>
> This should also encourage patch submitters to add him to the CC list.
Thank you for your ACK!
Now in our tree ("fixes" for -net):
New patches for t/upstream-net and t/upstream:
- 6f7b2f2a1d67: MAINTAINERS: add Geliang as reviewer for MPTCP
- Results: e16ff7eaad4e..c09cb0246e41 (export-net)
- Results: 79ba5831f60e..9adfb88a4930 (export)
Tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export-net/20231219T122647
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20231219T122647
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2023-12-19 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 14:45 [PATCH mptcp-net] MAINTAINERS: add Geliang as reviewer for MPTCP Matthieu Baerts
2023-12-15 15:46 ` Geliang Tang
2023-12-15 17:03 ` MAINTAINERS: add Geliang as reviewer for MPTCP: Tests Results MPTCP CI
2023-12-15 18:13 ` [PATCH mptcp-net] MAINTAINERS: add Geliang as reviewer for MPTCP Mat Martineau
2023-12-15 19:21 ` MAINTAINERS: add Geliang as reviewer for MPTCP: Tests Results MPTCP CI
2023-12-19 12:28 ` Matthieu Baerts [this message]
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=3cacaa5d-3951-4bbf-a7df-070021903510@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang.tang@linux.dev \
--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.