Netdev List
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: Qing Ming <a0yami@mailbox.org>,
	Sabrina Dubroca <sd@queasysnail.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"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] ovpn: avoid putting unrelated P2P peer on socket release
Date: Thu, 28 May 2026 11:11:58 +0100	[thread overview]
Message-ID: <20260528101158.GR2256768@horms.kernel.org> (raw)
In-Reply-To: <10ea92d8-f4f6-462a-a76d-729cfa1715e1@openvpn.net>

On Wed, May 27, 2026 at 02:45:03PM +0200, Antonio Quartulli wrote:
> Hi,
> 
> On 27/05/2026 10:55, Simon Horman wrote:
> > On Sat, May 23, 2026 at 04:15:43PM +0800, Qing Ming wrote:

...

> > It is probably not necessary to resubmit because of this,
> > but for future reference bug fixes for code present in the net tree
> > should be targeted at that tree like this:
> > 
> > 	Subject: [PATCH net] ...
> > 
> > You can see more about the Networking development workflow here:
> > https://docs.kernel.org/process/maintainer-netdev.html
> > 
> 
> Thanks for spotting this!
> I'll queue this patch in my tree and send it to net soon.
> 
> > 
> > FTR, there is an AI-generated review of this patchset available on
> > sashiko.dev. I do not believe it should effect the progress of this patch.
> > But, rather, be considered in the context of possible follow-up.
> > 
> 
> We are already actively working on all pre-existing issues.
> 
> Posted fixes can be seen on the openvpn-devel mailing list.
> 
> We are triaging patches there first (Sashiko is picking them up too) to
> avoid clogging netdev.

Thanks Antonio, got it.

...

  reply	other threads:[~2026-05-28 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23  8:15 [PATCH] ovpn: avoid putting unrelated P2P peer on socket release Qing Ming
2026-05-27  8:55 ` Simon Horman
2026-05-27 12:45   ` Antonio Quartulli
2026-05-28 10:11     ` Simon Horman [this message]
2026-05-27 12:42 ` Antonio Quartulli

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=20260528101158.GR2256768@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=a0yami@mailbox.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=antonio@openvpn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    /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