From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v3 3/4] net/netvsc: add documentation
Date: Wed, 18 Apr 2018 09:03:02 -0700
Message-ID: <20180418090302.7ad48010@xeon-e3>
References: <20180417215324.8576-1-sthemmin@microsoft.com>
 <20180417215324.8576-4-sthemmin@microsoft.com>
 <a5bc481b-dbb6-fca2-9c3b-9dfc2bf91cd5@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pl0-f67.google.com (mail-pl0-f67.google.com
 [209.85.160.67]) by dpdk.org (Postfix) with ESMTP id 781AD5F25
 for <dev@dpdk.org>; Wed, 18 Apr 2018 18:03:05 +0200 (CEST)
Received: by mail-pl0-f67.google.com with SMTP id k9-v6so1379405pll.12
 for <dev@dpdk.org>; Wed, 18 Apr 2018 09:03:05 -0700 (PDT)
In-Reply-To: <a5bc481b-dbb6-fca2-9c3b-9dfc2bf91cd5@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Wed, 18 Apr 2018 14:25:22 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 4/17/2018 10:53 PM, Stephen Hemminger wrote:
> > Matching documentation for new netvsc device.
> > 
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> > ---
> >  doc/guides/nics/index.rst              |  1 +
> >  doc/guides/nics/netvsc.rst             | 97 ++++++++++++++++++++++++++
> >  doc/guides/rel_notes/release_18_05.rst |  6 ++
> >  3 files changed, 104 insertions(+)
> >  create mode 100644 doc/guides/nics/netvsc.rst  
> 
> Documentation added for network driver but not for bus driver, does it make
> sense to add vmbus doc too?

Not really, vmbus is only useful for one network device.
What did Dpaa2 do?

> > diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
> > index bc9cdda6af7a..0a7b65d49293 100644
> > --- a/doc/guides/rel_notes/release_18_05.rst
> > +++ b/doc/guides/rel_notes/release_18_05.rst
> > @@ -115,6 +115,12 @@ New Features
> >  
> >    Linux uevent is supported as backend of this device event notification framework.
> >  
> > +* **Added experimental support for Hyper-V netvsc PMD.**
> > +
> > +  The new experimntal ``netvsc`` poll mode driver provides native support for
> > +  networking on Hyper-V. See the :doc:`../nics/netvsc` nic driver guide
> > +  for more details on this   new driver.
> > +  
> 
> Also there is a "Shared Library Versions" section of the release notes, the
> libraries with public API should be listed here with version information. I can
> see some bus libraries are there.
> 
> If any of the libraries added has public API, should be added into that list.

The vmbus is internal.