From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John McNamara <john.mcnamara@intel.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v1] doc: fix relative path of Nic table input file
Date: Mon, 5 Dec 2016 10:19:54 +0000 [thread overview]
Message-ID: <309bd474-f338-4626-3d94-dafe9d1dd706@intel.com> (raw)
In-Reply-To: <1480870057-1674-1-git-send-email-john.mcnamara@intel.com>
On 12/4/2016 4:47 PM, John McNamara wrote:
> Fix relative path between sphinx conf.py file and Nic table file
> to allow automatic build on ReadTheDocs.
>
> Fixes: 9db3f52126fb ("doc: generate NIC overview table from ini files")
>
> Signed-off-by: John McNamara <john.mcnamara@intel.com>
Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2016-12-05 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 16:47 John McNamara
2016-12-05 10:19 ` Ferruh Yigit [this message]
2016-12-05 15:15 ` [dpdk-stable] [dpdk-dev] " De Lara Guarch, Pablo
2016-12-06 16:31 ` 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=309bd474-f338-4626-3d94-dafe9d1dd706@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=stable@dpdk.org \
/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).