All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John McNamara <john.mcnamara@intel.com>, dev@dpdk.org
Subject: Re: [PATCH v2] doc: autogenerate nic overview table from ini files
Date: Tue, 19 Jul 2016 14:08:04 +0100	[thread overview]
Message-ID: <578E2634.1020303@intel.com> (raw)
In-Reply-To: <1468760340-27312-1-git-send-email-john.mcnamara@intel.com>

On 7/17/2016 1:59 PM, John McNamara wrote:
> Convert the NIC feature table in the overview doc into a set of ini
> files and add functions into the Sphinx conf.py file to auto-generate
> them back into an RST table.
> 
> The reason for doing this is to make it easier for PMD maintainers to
> update the feature matrix that makes up the table and to avoid
> frequent and hard to resolve conflicts in doc/guides/nics/overview.rst.
> 
> A NIC/PMD feature matrix is now an ini file like the following:
> 
>     $ head doc/guides/nics/nic_features/i40e.ini
>     ;
>     ; Features of the i40e network driver.
>     ;
>     [Features]
>     Link status          = Y
>     Link status event    = Y
>     Rx interrupt         = Y
>     Queue start/stop     = Y
>     ...
> 
> The output RST table matches the existing table with the column
> headers sorted.
> 
> Signed-off-by: John McNamara <john.mcnamara@intel.com>

Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2016-07-19 13:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 18:03 [PATCH v1] doc: autogenerate nic overview table from ini files John McNamara
2016-06-30 18:03 ` John McNamara
2016-06-30 18:25 ` Thomas Monjalon
2016-07-01  1:40   ` Yuanhan Liu
2016-07-08 19:52   ` Mcnamara, John
2016-07-17 12:59 ` [PATCH v2] " John McNamara
2016-07-19 13:08   ` Ferruh Yigit [this message]
2016-07-29 11:59 ` [PATCH v3] " John McNamara
2016-07-29 12:02   ` Mcnamara, John
2016-08-01 21:37   ` Thomas Monjalon
2016-08-03 14:32     ` Bruce Richardson
2016-08-03 16:44       ` Thomas Monjalon

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=578E2634.1020303@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.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.