From: Paul Bolle <pebolle@tiscali.nl>
To: Dexuan Cui <decui@microsoft.com>
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
driverdev-devel@linuxdriverproject.org, olaf@aepfle.de,
apw@canonical.com, jasowang@redhat.com, kys@microsoft.com,
haiyangz@microsoft.com
Subject: Re: [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature
Date: Tue, 07 Jul 2015 11:37:56 +0200 [thread overview]
Message-ID: <1436261876.20057.132.camel@tiscali.nl> (raw)
In-Reply-To: <1436194049-27829-1-git-send-email-decui@microsoft.com>
Just two nits.
On ma, 2015-07-06 at 07:47 -0700, Dexuan Cui wrote:
> --- /dev/null
> +++ b/net/hv_sock/Kconfig
> +config HYPERV_SOCK
> + tristate "Microsoft Hyper-V Socket (EXPERIMENTAL)"
> + depends on HYPERV
> + default m
> + help
> + Hyper-V Socket is a socket protocol similar to TCP, allowing
> + communication between a Linux guest and the host.
> +
> + To compile this driver as a module, choose M here: the module
> + will be called hv_sock. If unsure, say N.
It's a bit odd to advise to say N if one is unsure and set the default
to 'm' at the same time.
> --- /dev/null
> +++ b/net/hv_sock/af_hvsock.c
> +static int hvsock_init(void)
> +{
> + [...]
> +}
> +
> +static void hvsock_exit(void)
> +{
> + [...]
> +}
> +
> +module_init(hvsock_init);
> +module_exit(hvsock_exit);
Any specific reason not to mark these functions __init and __exit?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-07-07 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:47 [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature Dexuan Cui
2015-07-07 9:37 ` Paul Bolle [this message]
2015-07-07 10:02 ` Dexuan Cui
2015-07-07 10:10 ` Olaf Hering
2015-07-07 10:20 ` Dexuan Cui
2015-07-07 10:58 ` Olaf Hering
2015-07-08 5:22 ` Dexuan Cui
2015-07-07 11:51 ` Paul Bolle
2015-07-07 18:31 ` Stephen Hemminger
2015-07-08 3:56 ` Dexuan Cui
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=1436261876.20057.132.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/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).