All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	John McNamara <john.mcnamara@intel.com>
Subject: Re: [PATCH v3 3/4] net/netvsc: add documentation
Date: Wed, 18 Apr 2018 17:16:14 +0100	[thread overview]
Message-ID: <5afa5b27-a343-840a-4190-378527ec6cfb@intel.com> (raw)
In-Reply-To: <20180418090302.7ad48010@xeon-e3>

On 4/18/2018 5:03 PM, Stephen Hemminger wrote:
> 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?

It seems they also only documented the drivers (net, crypto, event).

There is no bus level documentation for any bus, if I am not missing them, not
sure if this is a gap?

> 
>>> 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.
> 

  reply	other threads:[~2018-04-18 16:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 21:53 [PATCH v3 0/4] Hyper-V Netvsc PMD Stephen Hemminger
2018-04-17 21:53 ` [PATCH v3 1/4] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-04-18 13:16   ` Ferruh Yigit
2018-04-18 16:01     ` Stephen Hemminger
2018-04-17 21:53 ` [PATCH v3 2/4] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-04-18 13:19   ` Ferruh Yigit
2018-04-18 16:04     ` Stephen Hemminger
2018-04-18 17:36     ` Stephen Hemminger
2018-04-17 21:53 ` [PATCH v3 3/4] net/netvsc: add documentation Stephen Hemminger
2018-04-18 13:25   ` Ferruh Yigit
2018-04-18 16:03     ` Stephen Hemminger
2018-04-18 16:16       ` Ferruh Yigit [this message]
2018-04-19 12:37         ` Hemant Agrawal
2018-04-17 21:53 ` [PATCH v3 4/4] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-04-18 13:25 ` [PATCH v3 0/4] Hyper-V Netvsc PMD Ferruh Yigit

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=5afa5b27-a343-840a-4190-378527ec6cfb@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=john.mcnamara@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.