From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v9 0/8] use GENL_REQ_ATTR_CHECK in userspace pm
Date: Sun, 12 Jan 2025 13:43:03 +0100 [thread overview]
Message-ID: <1c4ec8dc-bbdf-4e3c-b31d-306286ed9bbf@kernel.org> (raw)
In-Reply-To: <fd65072a-7bca-4b15-b184-b1213eecafca@kernel.org>
Hi Geliang,
On 10/01/2025 12:21, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 10/01/2025 08:30, Geliang Tang wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> v9:
>> patch 3, move the code using NL_SET_ERR_MSG_ATTR into patch 8.
>> patch 7, adjust the location of "pernet = pm_nl_get_pernet(net);".
>
> Thank you for the new version.
>
> I have one small request in patch 8/8, but I can fix that when applying
> the patches if that's OK with you.
>
> I can also do the modifications in set_flags(), and fix the conflicts
> when applying "BPF path manager, part 2" (if it is ready)
As discussed on the "BPF path manager, part 2" thread, I will apply
patches from these 2 series with the suggested modifications.
Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-01-12 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 7:30 [PATCH mptcp-next v9 0/8] use GENL_REQ_ATTR_CHECK in userspace pm Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 1/8] mptcp: drop info of userspace_pm_remove_id_zero_address Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 2/8] mptcp: pm: userspace: flags: clearer msg if no remote addr Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 3/8] mptcp: pm: more precise error messages Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 4/8] mptcp: pm: improve " Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 5/8] mptcp: pm: userspace: use GENL_REQ_ATTR_CHECK Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 6/8] mptcp: pm: remove duplicated error messages Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 7/8] mptcp: pm: mark missing address attributes Geliang Tang
2025-01-10 7:30 ` [PATCH mptcp-next v9 8/8] mptcp: pm: use NL_SET_ERR_MSG_ATTR when possible Geliang Tang
2025-01-10 11:48 ` Matthieu Baerts
2025-01-10 8:35 ` [PATCH mptcp-next v9 0/8] use GENL_REQ_ATTR_CHECK in userspace pm MPTCP CI
2025-01-10 11:21 ` Matthieu Baerts
2025-01-12 12:43 ` Matthieu Baerts [this message]
2025-01-12 12:57 ` 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=1c4ec8dc-bbdf-4e3c-b31d-306286ed9bbf@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox