From: Antonio Quartulli <antonio@openvpn.net>
To: chuguangqing <chuguangqing@inspur.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, Sabrina Dubroca <sd@queasysnail.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH v2 1/1] ovpn: use kmalloc_array() for array space allocation
Date: Wed, 3 Sep 2025 10:41:01 +0200 [thread overview]
Message-ID: <0c104f3d-5ee6-4d07-a183-62d603ce56df@openvpn.net> (raw)
In-Reply-To: <20250902090051.1451-2-chuguangqing@inspur.com>
Hello and thanks a lot for contribution!
This is indeed a nice improvement, however, we've been working on
changing this part of the code.
We already have a pending commit in the queue (to be sent to net-next
soonish):
https://github.com/mandelbitdev/ovpn-net-next/commit/9b62844193de705502fdf4a693dfe0f6c7d94f13
With the mentioned patch, the line you are changing does not exist
anymore, therefore I don't think it makes sense to merge your patch
first and then removing it again in the next commit.
Sorry about this!
Please feel free to stick around and submit more patches in the future!
Regards,
--
Antonio Quartulli
OpenVPN Inc.
next prev parent reply other threads:[~2025-09-03 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 11:21 [PATCH 1/1] ovpn: use kmalloc_array() for array space allocation chuguangqing
2025-09-02 8:18 ` Simon Horman
2025-09-02 9:00 ` PATCH v2 Re: " chuguangqing
2025-09-02 9:00 ` [PATCH v2 " chuguangqing
2025-09-02 13:15 ` Markus Elfring
2025-09-03 12:17 ` chuguangqing
2025-09-03 12:54 ` [v2] " Markus Elfring
2025-09-03 8:41 ` Antonio Quartulli [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-03 12:00 [PATCH v2 1/1] " Gary Chu(楚光庆)
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=0c104f3d-5ee6-4d07-a183-62d603ce56df@openvpn.net \
--to=antonio@openvpn.net \
--cc=andrew+netdev@lunn.ch \
--cc=chuguangqing@inspur.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 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.