From: Olaf Hering <olaf@aepfle•de>
To: Dexuan Cui <decui@microsoft•com>
Cc: "gregkh@linuxfoundation•org" <gregkh@linuxfoundation•org>,
"jasowang@redhat•com" <jasowang@redhat•com>,
Haiyang Zhang <haiyangz@microsoft•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"joe@perches•com" <joe@perches•com>,
Rolf Neugebauer <rolf.neugebauer@docker•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"apw@canonical•com" <apw@canonical•com>,
"devel@linuxdriverproject•org" <devel@linuxdriverproject•org>,
Vitaly Kuznetsov <vkuznets@redhat•com>,
"davem@davemloft•net" <davem@davemloft•net>
Subject: Re: [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets
Date: Thu, 30 Jun 2016 18:12:12 +0200 [thread overview]
Message-ID: <20160630161212.GA7456@aepfle.de> (raw)
In-Reply-To: <CY1PR03MB21865E21E637F03877784979BF240@CY1PR03MB2186.namprd03.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 221 bytes --]
On Thu, Jun 30, Dexuan Cui wrote:
> -#define AF_MAX 43 /* For now.. */
> +#define AF_MAX 44 /* For now.. */
Should this patch also change the places where AF_MAX is used,
like all the arrays in net/core/sock.c?
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
devel mailing list
devel@linuxdriverproject•org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2016-06-30 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 15:58 [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui
2016-06-30 16:12 ` Olaf Hering [this message]
2016-06-30 16:22 ` Dexuan Cui
2016-07-01 6:42 ` Olaf Hering
2016-07-05 1:58 ` Dexuan Cui
2016-07-05 6:27 ` David Miller
2016-07-05 6:46 ` Dexuan Cui
2016-07-05 6:58 ` David Miller
2016-07-05 8:21 ` Joe Perches
2016-07-05 9:31 ` Dexuan Cui
2016-07-05 9:38 ` Joe Perches
2016-07-05 10:46 ` Dexuan Cui
2016-07-07 16:02 ` Olaf Hering
2016-07-08 7:01 ` 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=20160630161212.GA7456@aepfle.de \
--to=olaf@aepfle$(echo .)de \
--cc=apw@canonical$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=decui@microsoft$(echo .)com \
--cc=devel@linuxdriverproject$(echo .)org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=haiyangz@microsoft$(echo .)com \
--cc=jasowang@redhat$(echo .)com \
--cc=joe@perches$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rolf.neugebauer@docker$(echo .)com \
--cc=vkuznets@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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