[Intel-wired-lan] [PATCH net-next V5 2/2] intel: ixgbevf: Support Windows hosts (Hyper-V)

[KY Srinivasan]

> -----Original Message-----
> From: Alexander Duyck [mailto:alexander.duyck at gmail.com]
> Sent: Wednesday, April 27, 2016 1:51 PM
> To: KY Srinivasan <kys at microsoft.com>; Jeff Kirsher
> <jeffrey.t.kirsher at intel.com>
> Cc: Bowers, AndrewX <andrewx.bowers at intel.com>; intel-wired-
> lan at lists.osuosl.org
> Subject: Re: [Intel-wired-lan] [PATCH net-next V5 2/2] intel: ixgbevf: Support
> Windows hosts (Hyper-V)
> 
> On Wed, Apr 27, 2016 at 11:33 AM, KY Srinivasan <kys at microsoft.com>
> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org]
> On
> >> Behalf Of Bowers, AndrewX
> >> Sent: Friday, April 22, 2016 12:32 PM
> >> To: intel-wired-lan at lists.osuosl.org
> >> Subject: Re: [Intel-wired-lan] [PATCH net-next V5 2/2] intel: ixgbevf:
> Support
> >> Windows hosts (Hyper-V)
> >>
> >> > -----Original Message-----
> >> > From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org]
> On
> >> > Behalf Of K. Y. Srinivasan
> >> > Sent: Tuesday, April 19, 2016 7:18 PM
> >> > To: davem at davemloft.net; netdev at vger.kernel.org; linux-
> >> > kernel at vger.kernel.org; devel at linuxdriverproject.org; olaf at aepfle.de;
> >> > apw at canonical.com; jasowang at redhat.com; eli at mellanox.com;
> >> > jackm at mellanox.com; yevgenyp at mellanox.com; Ronciak, John
> >> > <john.ronciak at intel.com>; intel-wired-lan at lists.osuosl.org;
> >> > alexander.duyck at gmail.com
> >> > Subject: [Intel-wired-lan] [PATCH net-next V5 2/2] intel: ixgbevf:
> Support
> >> > Windows hosts (Hyper-V)
> >> >
> >> > On Hyper-V, the VF/PF communication is a via software mediated path
> as
> >> > opposed to the hardware mailbox. Make the necessary adjustments to
> >> > support Hyper-V.
> >> >
> >> > Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
> >> > ---
> >> >     V2: Addressed most of the comments from
> >> >         Alexander Duyck <alexander.duyck at gmail.com>
> >> >         and Rustad, Mark D <mark.d.rustad at intel.com>.
> >> >
> >> >     V3: Addressed additional comments from
> >> >         Alexander Duyck <alexander.duyck at gmail.com>
> >> >
> >> >     V4: Addressed kbuild errors reported by:
> >> >         kbuild test robot <lkp at intel.com>
> >> >
> >> >     V5: Addressed additional comments from
> >> >         Alexander Duyck <alexander.duyck at gmail.com>
> >> >
> >> >  drivers/net/ethernet/intel/ixgbevf/ixgbevf.h      |   12 ++
> >> >  drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c |   31 +++-
> >> >  drivers/net/ethernet/intel/ixgbevf/mbx.c          |   12 ++
> >> >  drivers/net/ethernet/intel/ixgbevf/vf.c           |  216
> >> > +++++++++++++++++++++
> >> >  drivers/net/ethernet/intel/ixgbevf/vf.h           |    2 +
> >> >  5 files changed, 266 insertions(+), 7 deletions(-)
> >>
> >> Tested-by: Andrew Bowers <andrewx.bowers at intel.com>
> >> VF driver correctly builds and changes correctly applied.
> >
> > Andrew,
> >
> > This is the first time I am submitting a patch to Intel. What is involved in
> getting this into David Miller's tree.
> > Should I submit these to net-next?
> >
> > K. Y
> 
> You just need to give them some time.  Jeff Kirsher will submit it
> from his tree to Dave Miller in a few weeks.  You just need to keep an
> eye on his queue at:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit.kern
> el.org%2fcgit%2flinux%2fkernel%2fgit%2fjkirsher%2fnext-
> queue.git%2flog%2f%3fh%3ddev-
> queue&data=01%7c01%7ckys%40microsoft.com%7cdd80981188ba475aeaf90
> 8d36edd933e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=i%2bVDU
> QghJmQO8DaubIHLSSkHg4fsoWzqA%2bhyD0LytD4%3d
> 
> They pull them off about 8 to 12 at time and submit them to Dave so
> that he can pull them into net-next.

Thanks Alex.

K. Y
> 
> - Alex