From: Tom Parkin <tparkin@katalix.com>
To: "Gong, Sishuai" <sishuai@purdue.edu>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Matthias Schiffer <mschiffer@universe-factory.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH v3] net: fix a concurrency bug in l2tp_tunnel_register()
Date: Tue, 27 Apr 2021 09:54:22 +0100 [thread overview]
Message-ID: <20210427085422.GA4585@katalix.com> (raw)
In-Reply-To: <E30A6022-C479-4F67-B945-BFF0472CE320@purdue.edu>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On Mon, Apr 26, 2021 at 13:04:44 +0000, Gong, Sishuai wrote:
> On Apr 26, 2021, at 4:59 AM, Tom Parkin <tparkin@katalix.com> wrote:
> For some reason I've not been seeing these patches, just the replies.
> I can't see it on lore.kernel.org either, unless I'm missing something
> obvious.
>
> Have the original mails cc'd netdev?
>
> I also noticed this problem. I CCed netdev@vger.kernel.org but
> this message didn’t show up in the maillist. Actually, I also
> CCed you in the original email but it looks like only Cong Wang
> could see it.
> Should I re-send this email?
> Thanks.
If you CC'd me in the first place and I didn't see it that's strange.
I got your initial "bug report" mail :-|
From the perspective of submitting the patch, I have no problem with
it being applied on the strength of Cong Wang's review.
Thanks for working on this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-04-27 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210421192430.3036-1-sishuai@purdue.edu>
2021-04-23 17:38 ` [PATCH v3] net: fix a concurrency bug in l2tp_tunnel_register() Cong Wang
2021-04-26 8:59 ` Tom Parkin
[not found] ` <E30A6022-C479-4F67-B945-BFF0472CE320@purdue.edu>
2021-04-27 8:54 ` Tom Parkin [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=20210427085422.GA4585@katalix.com \
--to=tparkin@katalix.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mschiffer@universe-factory.net \
--cc=netdev@vger.kernel.org \
--cc=sishuai@purdue.edu \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.