[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BLUPR03MB14108769385C992B84F3C4AFBF900@BLUPR03MB1410.namprd03.prod.outlook.com>
Date: Thu, 7 Apr 2016 04:52:30 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next] net: add the AF_KCM entries to family name
tables
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Thursday, April 7, 2016 11:59
> To: Dexuan Cui <decui@...rosoft.com>
> Cc: netdev@...r.kernel.org
> Subject: Re: [PATCH net-next] net: add the AF_KCM entries to family name
> tables
>
> From: Dexuan Cui <decui@...rosoft.com>
> Date: Thu, 7 Apr 2016 01:54:18 +0000
>
> > Can you please apply this to net-next too?
>
> That will happen transparently the next time I merge 'net' into
> 'net-next'.
>
> It will happen at a time of my own choosing, and usually occurs
> when I do a push of my 'net' tree to Linus and he takes it in,
> and I know people need some 'net' things in 'net-next'.
Thanks for the explanation!
So, at present, let me only post the single AF_HYPERV patch to
net-next and hold the patch that adds AF_HYPERV entries to the family
name tables.
Thanks,
-- Dexuan
Powered by blists - more mailing lists