From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Stephen Hemminger <sthemmin@microsoft.com>,
John McNamara <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 3/4] net/netvsc: add documentation
Date: Thu, 19 Apr 2018 12:37:01 +0000 [thread overview]
Message-ID: <AM2PR04MB0753FD5FEDB197507BA3AD1B89B50@AM2PR04MB0753.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <5afa5b27-a343-840a-4190-378527ec6cfb@intel.com>
Hi Ferruh,
> 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?
>
[Hemant] dpaa2 bus documentation is embedded within the net/dpaa2 drivers.
Regards,
Hemant
next prev parent reply other threads:[~2018-04-19 12:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:53 [dpdk-dev] [PATCH v3 0/4] Hyper-V Netvsc PMD Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [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 ` [dpdk-dev] [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 ` [dpdk-dev] [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
2018-04-19 12:37 ` Hemant Agrawal [this message]
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 4/4] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-04-18 13:25 ` [dpdk-dev] [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=AM2PR04MB0753FD5FEDB197507BA3AD1B89B50@AM2PR04MB0753.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).