From: Matthieu Baerts <matttbe@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 01/15] mptcp: pm: drop info of userspace_pm_remove_id_zero_address
Date: Tue, 11 Feb 2025 10:31:05 +0100 [thread overview]
Message-ID: <adeff1d6-f80b-4a2c-b4bb-da44ecd5b747@kernel.org> (raw)
In-Reply-To: <20250210194934.GO554665@kernel.org>
Hi Simon,
On 10/02/2025 20:49, Simon Horman wrote:
> On Fri, Feb 07, 2025 at 02:59:19PM +0100, Matthieu Baerts (NGI0) wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> The only use of 'info' parameter of userspace_pm_remove_id_zero_address()
>> is to set an error message into it.
>>
>> Plus, this helper will only fail when it cannot find any subflows with a
>> local address ID 0.
>>
>> This patch drops this parameter and sets the error message where this
>> function is called in mptcp_pm_nl_remove_doit().
>>
>> 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>
>
> Reviewed-by: Simon Horman <horms@kernel.org>
Thank you for the review, and this message!
> A minor nit, perhaps it has been discussed before:
>
> I'm not sure that your Reviewed-by is needed if you also provide
> your Signed-off-by. Because it I think that the latter implies the former.
This has been discussed a while ago, but only on the MPTCP list I think.
To be honest, we didn't find a precise answer in the doc [1], and maybe
we are doing it wrong for all this time :)
Technically, when someone shares a patch on the MPTCP ML, someone else
does the review, sent the "Reviewed-by" tag, then the patch is queued,
and the one sending the patch to the netdev ML adds a "Signed-off-by"
tag. With this patch here, I did both.
Before, we were removing the RvB tag when it was the same as the SoB
one, but we stopped doing that because we thought that was not correct
and / or not needed. We can re-introduce this if preferred. My
understanding is that the SoB tag is for the authors and the
intermediate maintainers -- who might have not done a full review --
while the RvB one seems to indicate that a "proper" review has been
done. If someone else does a review on a patch, I can add my SoB tag
when "forwarding" the patch, trusting the review done by someone else.
Do you think it is better to remove the RvB tag if there is a SoB one
for the same person?
[1] https://docs.kernel.org/process/submitting-patches.html
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-02-11 9:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 13:59 [PATCH net-next v3 00/15] mptcp: pm: misc cleanups, part 2 Matthieu Baerts (NGI0)
2025-02-07 13:59 ` [PATCH net-next v3 01/15] mptcp: pm: drop info of userspace_pm_remove_id_zero_address Matthieu Baerts (NGI0)
2025-02-10 19:49 ` Simon Horman
2025-02-11 9:31 ` Matthieu Baerts [this message]
2025-02-11 10:13 ` Simon Horman
2025-02-11 10:21 ` Matthieu Baerts
2025-02-07 13:59 ` [PATCH net-next v3 02/15] mptcp: pm: userspace: flags: clearer msg if no remote addr Matthieu Baerts (NGI0)
2025-02-10 19:49 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 03/15] mptcp: pm: more precise error messages Matthieu Baerts (NGI0)
2025-02-10 19:50 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 04/15] mptcp: pm: improve " Matthieu Baerts (NGI0)
2025-02-10 19:50 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 05/15] mptcp: pm: userspace: use GENL_REQ_ATTR_CHECK Matthieu Baerts (NGI0)
2025-02-10 19:50 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 06/15] mptcp: pm: remove duplicated error messages Matthieu Baerts (NGI0)
2025-02-10 19:50 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 07/15] mptcp: pm: mark missing address attributes Matthieu Baerts (NGI0)
2025-02-10 19:51 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 08/15] mptcp: pm: use NL_SET_ERR_MSG_ATTR when possible Matthieu Baerts (NGI0)
2025-02-10 19:51 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 09/15] mptcp: pm: make three pm wrappers static Matthieu Baerts (NGI0)
2025-02-10 19:51 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 10/15] mptcp: pm: drop skb parameter of get_addr Matthieu Baerts (NGI0)
2025-02-10 19:51 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 11/15] mptcp: pm: add id parameter for get_addr Matthieu Baerts (NGI0)
2025-02-10 19:52 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 12/15] mptcp: pm: reuse sending nlmsg code in get_addr Matthieu Baerts (NGI0)
2025-02-10 19:52 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 13/15] mptcp: pm: drop skb parameter of set_flags Matthieu Baerts (NGI0)
2025-02-10 19:52 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 14/15] mptcp: pm: change rem type " Matthieu Baerts (NGI0)
2025-02-10 19:52 ` Simon Horman
2025-02-07 13:59 ` [PATCH net-next v3 15/15] mptcp: pm: add local parameter for set_flags Matthieu Baerts (NGI0)
2025-02-10 19:52 ` Simon Horman
2025-02-11 12:00 ` [PATCH net-next v3 00/15] mptcp: pm: misc cleanups, part 2 patchwork-bot+netdevbpf
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=adeff1d6-f80b-4a2c-b4bb-da44ecd5b747@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;
as well as URLs for NNTP newsgroup(s).