public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>,
	mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 11/15] mptcp: pm: add id parameter for get_addr
Date: Sat, 18 Jan 2025 08:44:24 +0100	[thread overview]
Message-ID: <93cae50d-2ede-46b6-9c4b-e18deefe3295@kernel.org> (raw)
In-Reply-To: <ffa8b3d7fee95ab196fe35a3a3d855653fccfb9e.camel@kernel.org>

Hi Geliang,

On 18/01/2025 00:28, Geliang Tang wrote:
> Hi Matt,
> 
> On Fri, 2025-01-17 at 19:41 +0100, Matthieu Baerts (NGI0) wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> The address id is parsed both in mptcp_pm_nl_get_addr() and
>> mptcp_userspace_pm_get_addr(), this makes the code somewhat
>> repetitive.
>>
>> So this patch adds a new parameter 'id' for all get_addr()
>> interfaces.
>> The address id is only parsed in mptcp_pm_nl_get_addr_doit(), then
>> pass
>> it to both mptcp_pm_nl_get_addr() and mptcp_userspace_pm_get_addr().
>>
>> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
>> Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> ---
>> v2:
>> - Fix 'attr' no longer being set in mptcp_pm_nl_get_addr(), but still
>>   used in this patch (no longer in the next one). (Simon)
> 
> mptcp_userspace_pm_get_addr() needs to be updated too.

Arf, I didn't think about pm_userspace.c :(
I should have definitively squashed patch 11 and 12...

That's OK, I will resend them later, simply moving the line removal from
patch 11 to 12.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2025-01-18  7:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 18:41 [PATCH net-next v2 00/15] mptcp: pm: misc cleanups, part 2 Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 01/15] mptcp: pm: drop info of userspace_pm_remove_id_zero_address Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 02/15] mptcp: pm: userspace: flags: clearer msg if no remote addr Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 03/15] mptcp: pm: more precise error messages Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 04/15] mptcp: pm: improve " Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 05/15] mptcp: pm: userspace: use GENL_REQ_ATTR_CHECK Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 06/15] mptcp: pm: remove duplicated error messages Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 07/15] mptcp: pm: mark missing address attributes Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 08/15] mptcp: pm: use NL_SET_ERR_MSG_ATTR when possible Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 09/15] mptcp: pm: make three pm wrappers static Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 10/15] mptcp: pm: drop skb parameter of get_addr Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 11/15] mptcp: pm: add id parameter for get_addr Matthieu Baerts (NGI0)
2025-01-17 23:28   ` Geliang Tang
2025-01-18  7:44     ` Matthieu Baerts [this message]
2025-01-17 18:41 ` [PATCH net-next v2 12/15] mptcp: pm: reuse sending nlmsg code in get_addr Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 13/15] mptcp: pm: drop skb parameter of set_flags Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 14/15] mptcp: pm: change rem type " Matthieu Baerts (NGI0)
2025-01-17 18:41 ` [PATCH net-next v2 15/15] mptcp: pm: add local parameter for set_flags Matthieu Baerts (NGI0)

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=93cae50d-2ede-46b6-9c4b-e18deefe3295@kernel.org \
    --to=matttbe@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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