From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@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: Sat, 18 Jan 2025 18:56:14 +0800 [thread overview]
Message-ID: <ce96e53625b87502979cb138a25798f4e07b2a88.camel@kernel.org> (raw)
In-Reply-To: <e34a54e2-bf7b-47eb-89ac-80e5605955aa@kernel.org>
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.
Thanks,
-Geliang
>
> Cheers,
> Matt
prev parent reply other threads:[~2025-01-18 10:56 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
2025-01-20 9:55 ` Geliang Tang
2025-01-18 10:56 ` Geliang Tang [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=ce96e53625b87502979cb138a25798f4e07b2a88.camel@kernel.org \
--to=geliang@kernel.org \
--cc=matttbe@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