DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
	Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v7] doc: document NIC features
Date: Sat, 05 Aug 2017 11:34:45 +0200	[thread overview]
Message-ID: <3295100.VjfkbcM1ud@xps> (raw)
In-Reply-To: <20170804130613.72410-1-ferruh.yigit@intel.com>

04/08/2017 15:06, Ferruh Yigit:
> Document NIC features, add more information about them and add more
> implementation related support.
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Signed-off-by: John McNamara <john.mcnamara@intel.com>
> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> ---
> --- /dev/null
> +++ b/doc/guides/nics/features.rst
> +.. _nic_features:
> +
> +Features Overview
> +=================
> +
> +This section explains the supported features that are listed in the
> +:ref:`nic_overview`.
[...]
> --- a/doc/guides/nics/overview.rst
> +++ b/doc/guides/nics/overview.rst
> +.. _nic_overview:
> +
>  Overview of Networking Drivers
>  ==============================
>  
> @@ -48,6 +50,8 @@ There are more differences between drivers regarding some internal properties,
>  portability or even documentation availability.
>  Most of these differences are summarized below.
>  
> +More detail about features can be found :ref:`here <nic_features>`.

No need of adding explicit ref to link to the beginning of a document.
I replace them with :doc: tag.

With this small update, applied, thanks

      parent reply	other threads:[~2017-08-05  9:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 16:37 [dpdk-dev] [RFC] " Ferruh Yigit
2017-06-21 13:25 ` [dpdk-dev] [PATCH] " Ferruh Yigit
2017-06-22 19:02   ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2017-07-02 20:20     ` Mcnamara, John
2017-07-05 13:20     ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2017-07-05 16:03       ` Mcnamara, John
2017-07-07 10:55       ` Andrew Rybchenko
2017-07-07 13:37         ` Ferruh Yigit
2017-07-07 13:53           ` Thomas Monjalon
2017-07-07 13:57             ` Ferruh Yigit
2017-07-07 14:02               ` Thomas Monjalon
2017-07-07 14:13                 ` Ferruh Yigit
2017-07-07 14:20                   ` Wiles, Keith
2017-07-07 20:37                     ` Thomas Monjalon
2017-07-07 23:54                       ` Wiles, Keith
2017-07-07 15:06         ` Ferruh Yigit
2017-07-07 15:38           ` Andrew Rybchenko
2017-07-07 17:21       ` [dpdk-dev] [PATCH v4] " Ferruh Yigit
2017-07-08  9:47         ` Andrew Rybchenko
2017-07-20  9:10           ` Ferruh Yigit
2017-07-20  9:23         ` [dpdk-dev] [PATCH v5] " Ferruh Yigit
2017-07-26  5:08           ` Shreyansh Jain
2017-08-01 10:15             ` Ferruh Yigit
2017-08-01 15:23           ` [dpdk-dev] [PATCH v6] " Ferruh Yigit
2017-08-03  8:56             ` Shreyansh Jain
2017-08-03  8:57               ` Shreyansh Jain
2017-08-03 10:42             ` Mcnamara, John
2017-08-03 22:57             ` Thomas Monjalon
2017-08-04  8:56               ` Ferruh Yigit
2017-08-04  9:32                 ` Thomas Monjalon
2017-08-04 10:04                   ` Ferruh Yigit
2017-08-04 10:10                     ` Thomas Monjalon
2017-08-04 11:11                   ` Mcnamara, John
2017-08-04 11:40                     ` Ferruh Yigit
2017-08-04 13:06             ` [dpdk-dev] [PATCH v7] " Ferruh Yigit
2017-08-04 13:34               ` Mcnamara, John
2017-08-05  9:34               ` Thomas Monjalon [this message]

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=3295100.VjfkbcM1ud@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=olivier.matz@6wind.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).