[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160704.232704.1161688488597729534.davem@davemloft.net>
Date: Mon, 04 Jul 2016 23:27:04 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: decui@...rosoft.com
Cc: gregkh@...uxfoundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
olaf@...fle.de, apw@...onical.com, jasowang@...hat.com,
vkuznets@...hat.com, cavery@...hat.com, kys@...rosoft.com,
haiyangz@...rosoft.com, joe@...ches.com, rolf.neugebauer@...ker.com
Subject: Re: [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets
From: Dexuan Cui <decui@...rosoft.com>
Date: Tue, 5 Jul 2016 01:58:31 +0000
> Not sure if you had a chance to review this version.
Why me?
Other people have to review this too.
> Now I have a question: may I split the include/linux/socket.h change
> and ask you to pre-allocate the number for AF_HYPERV to allow
> backporting of Hyper-V Sockets to distro kernels, and to make sure
> that applications using the socket type will work with the backport
> as well as the upstream kernel?
Sorry, I'm not going to do this.
You cannot commit anything in userspace to this value anywhere
until it is accepted upstream.
Powered by blists - more mailing lists