[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1219c53f-362e-cd55-73e0-87dfe281ec34@openvpn.net>
Date: Wed, 3 Aug 2022 17:48:45 +0200
From: Antonio Quartulli <antonio@...nvpn.net>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [RFC 1/1] net: introduce OpenVPN Data Channel Offload (ovpn-dco)
Hi Stephen,
On 03/08/2022 17:42, Stephen Hemminger wrote:
> Kernel submissions for upstream must be standalone, and any infrastructure
> that is only used by an out of tree kernel driver will not be accepted.
>
> The version you propose upstream must have no linux-compat wrappers.
> Sorry kernel developers don't care or want to be concerned about some
> out of tree project.
There must have been some confusion - sorry about that.
The repository I linked in my previous email is this very same driver
packaged as "out-of-tree" module (i.e. for people running a kernel that
does not yet ship ovpn-dco) and contains some compat wrapper.
The driver I have submitted to the list is 100% standalone and does not
contain any compat code.
The only extra component required to do something useful with this
driver is the OpenVPN software in userspace.
I hope this clarifies.
Regards,
--
Antonio Quartulli
OpenVPN Inc.
Powered by blists - more mailing lists