From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andres Salomon <dilinger@queued.net>,
linux-geode@lists.infradead.org, Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Christian Gromm <christian.gromm@microchip.com>,
Krzysztof Halasa <khc@pm.waw.pl>,
Netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Martin Schiller <ms@dev.tdt.de>,
linux-x25@vger.kernel.org,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH 6/6] net: wireguard: rename 'mod_init' & 'mod_exit' functions to be module-specific
Date: Fri, 9 Jul 2021 12:21:39 +0200 [thread overview]
Message-ID: <CAHmME9rUJndFC-6KAxGL3w6Ka4WgyP_m5DS+1_vuHdQowonSOg@mail.gmail.com> (raw)
In-Reply-To: <20210709021747.32737-7-rdunlap@infradead.org>
Hi Randy,
The commit subject line should be:
wireguard: main: rename 'mod_init' & 'mod_exit' functions to be module-specific
And:
On Fri, Jul 9, 2021 at 4:17 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> -static int __init mod_init(void)
> +static int __init wireguard_init(void)
wg_mod_init
> -static void __exit mod_exit(void)
> +static void __exit wireguard_exit(void)
wg_mod_exit
Thanks,
Jason
prev parent reply other threads:[~2021-07-09 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 2:17 [PATCH 0/6] treewide: " Randy Dunlap
2021-07-09 2:17 ` [PATCH 1/6] arm: crypto: " Randy Dunlap
2021-07-09 2:17 ` [PATCH 2/6] hw_random: " Randy Dunlap
2021-07-09 2:17 ` [PATCH 3/6] lib: crypto: " Randy Dunlap
2021-07-09 2:17 ` [PATCH 4/6] MOST: cdev: " Randy Dunlap
2021-07-09 2:17 ` [PATCH 5/6] net: hdlc: " Randy Dunlap
2021-07-09 2:17 ` [PATCH 6/6] net: wireguard: " Randy Dunlap
2021-07-09 10:21 ` Jason A. Donenfeld [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=CAHmME9rUJndFC-6KAxGL3w6Ka4WgyP_m5DS+1_vuHdQowonSOg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=christian.gromm@microchip.com \
--cc=davem@davemloft.net \
--cc=dilinger@queued.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=khc@pm.waw.pl \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-geode@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mpm@selenic.com \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=wireguard@lists.zx2c4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).