From: Jakub Kicinski <kuba@kernel.org>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/1] net: introduce OpenVPN Data Channel Offload (ovpn-dco)
Date: Thu, 28 Jul 2022 09:28:48 -0700 [thread overview]
Message-ID: <20220728092848.36c6ccd5@kernel.org> (raw)
In-Reply-To: <c490b87c-085b-baca-b7e4-c67a3ee2c25e@openvpn.net>
On Thu, 28 Jul 2022 09:41:11 +0200 Antonio Quartulli wrote:
> However, I guess I will still fill MODULE_VERSION() with a custom
> string. This may also be useful when building the module out-of-tree.
Please use the kernel versions for versioning the out of tree code.
Whenever a new release is cut upstream you bump the number
appropriately in oot, and adjust whatever compat code needs adjusting.
next prev parent reply other threads:[~2022-07-28 16:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 1:47 [RFC 0/1] Introducing OpenVPN Data Channel Offload Antonio Quartulli
2022-07-19 1:47 ` [RFC 1/1] net: introduce OpenVPN Data Channel Offload (ovpn-dco) Antonio Quartulli
2022-07-19 15:19 ` Andrew Lunn
2022-07-19 15:21 ` Antonio Quartulli
2022-07-19 15:25 ` Andrew Lunn
2022-07-28 7:41 ` Antonio Quartulli
2022-07-28 13:07 ` Andrew Lunn
2022-07-28 13:16 ` Antonio Quartulli
2022-08-03 15:42 ` Stephen Hemminger
2022-08-03 15:48 ` Antonio Quartulli
2022-08-03 16:19 ` Stephen Hemminger
2022-08-04 7:34 ` Antonio Quartulli
2022-07-28 16:28 ` Jakub Kicinski [this message]
2022-07-28 19:16 ` Antonio Quartulli
2022-07-19 15:37 ` Andrew Lunn
2022-07-28 7:44 ` Antonio Quartulli
2022-07-28 13:12 ` Andrew Lunn
2022-08-03 15:31 ` [RFC v2] " Antonio Quartulli
2022-08-12 18:34 ` Sergey Ryazanov
2022-08-12 18:44 ` Stephen Hemminger
2022-08-30 22:35 ` Sergey Ryazanov
2022-08-12 21:05 ` Antonio Quartulli
2022-08-31 3:15 ` Sergey Ryazanov
2022-09-09 20:40 ` Antonio Quartulli
2022-09-13 0:49 ` Sergey Ryazanov
2022-08-03 16:04 ` [RFC 1/1] " Joe Perches
2022-08-04 7:35 ` 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=20220728092848.36c6ccd5@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=antonio@openvpn.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.