From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang.tang@linux.dev>,
Florian Westphal <fw@strlen.de>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
syzbot+2a6fbf0f0530375968df@syzkaller.appspotmail.com,
Geliang Tang <geliang@kernel.org>,
MPTCP Linux <mptcp@lists.linux.dev>,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH v2 net] mptcp: fix a race in mptcp_pm_del_add_timer()
Date: Mon, 17 Nov 2025 17:05:08 -0800 [thread overview]
Message-ID: <20251117170508.4ffe043f@kernel.org> (raw)
In-Reply-To: <a155bf8b-08cd-4cd9-91d9-f49180f19f6c@kernel.org>
On Mon, 17 Nov 2025 11:42:31 +0100 Matthieu Baerts wrote:
> >> Out of curiosity, is it not OK to reply to the patch with the new
> >> Reported-by & Closes tags to have them automatically added when applying
> >> the patch? (I was going to do that on the v1, then I saw the v2 just
> >> when I was going to press 'Send' :) )
> >
> > I am not sure patchwork has been finally changed to understand these two tags.
>
> Ah yes, thank you! If there is a dependence on Patchwork, I think
> indeed, it doesn't recognise the 'Closes' tag (but I think 'Reported-by'
> is OK).
>
> While at it, I forgot to add: this patch can be applied in net directly.
FWIW I have a local script which extracts them from patchwork comments
and applies them (same for Fixes tags). But it's always safer to resend.
next prev parent reply other threads:[~2025-11-18 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 10:07 [PATCH v2 net] mptcp: fix a race in mptcp_pm_del_add_timer() Eric Dumazet
2025-11-17 10:15 ` Matthieu Baerts
2025-11-17 10:21 ` Eric Dumazet
2025-11-17 10:42 ` Matthieu Baerts
2025-11-18 1:05 ` Jakub Kicinski [this message]
2025-11-18 2:35 ` Matthieu Baerts
2025-11-19 3:20 ` 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=20251117170508.4ffe043f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=geliang.tang@linux.dev \
--cc=geliang@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+2a6fbf0f0530375968df@syzkaller.appspotmail.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).