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] Squash to "mptcp: pm: add id parameter for get_addr"
Date: Mon, 20 Jan 2025 09:20:48 +0100 [thread overview]
Message-ID: <381923ac-bb94-4386-90a3-7d9cde7ed468@kernel.org> (raw)
In-Reply-To: <44df209fd690c009ddbcafd5e2a6872b987da4e2.camel@kernel.org>
Hi Geliang,
On 18/01/2025 11:54, Geliang Tang wrote:
> Hi Matt,
>
> On Sat, 2025-01-18 at 08:50 +0100, Matthieu Baerts wrote:
>> Hi Geliang,
>>
>> On 18/01/2025 00:26, Geliang Tang wrote:
>>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>>
>>> No need to drop 'attr = info->attrs[MPTCP_PM_ENDPOINT_ADDR];' in
>>> mptcp_userspace_pm_get_addr() too, add it back.
>>>
>>> Alse update mptcp_pm_nl_get_addr() to keep the original two-line
>>> assignment of 'attr'.
>>
>> I did a simple fix instead, see 648a0809e4cf ("Squash to "mptcp: pm:
>> add
>> id parameter for get_addr"") and the final export branch. Tell me if
>> that's not OK.
>
> It works.
>
> But we just change
>
> struct nlattr *token = info->attrs[MPTCP_PM_ATTR_TOKEN];
>
> to
> struct nlattr *token;
>
> token = info->attrs[MPTCP_PM_ATTR_TOKEN];
>
> in patch 5 "mptcp: pm: userspace: use GENL_REQ_ATTR_CHECK".
>
> We change it back again in this patch 11.
>
> So I prefer to use the two-line assignment of 'attr'. But up to you.
I see, it makes sense. But well, at the end, this code is going to be
moved elsewhere. Because the modifications have already been done
internally, I think it is fine to leave them like that, and avoid
dealing with new conflicts.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-01-20 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 23:26 [PATCH mptcp-next] Squash to "mptcp: pm: add id parameter for get_addr" Geliang Tang
2025-01-18 7:50 ` Matthieu Baerts
2025-01-18 10:54 ` Geliang Tang
2025-01-20 8:20 ` Matthieu Baerts [this message]
2025-01-20 9:55 ` Geliang Tang
2025-01-18 10:56 ` Geliang Tang
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=381923ac-bb94-4386-90a3-7d9cde7ed468@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