From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: hemant.agrawal@nxp.com, dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: fix DPAA2 guide build warning
Date: Mon, 27 Mar 2017 12:12:24 +0100 [thread overview]
Message-ID: <df16cb56-62ff-bba6-8d17-119c51177c92@intel.com> (raw)
In-Reply-To: <7137b742-c16e-82a2-2acd-2d052d5a2c26@intel.com>
On 3/27/2017 10:57 AM, Ferruh Yigit wrote:
> On 3/27/2017 10:57 AM, Shreyansh Jain wrote:
>> On Monday 27 March 2017 03:25 PM, Shreyansh Jain wrote:
>>> Fixes: 17a4c3c16f5c ("doc: add DPAA2 NIC details")
>>>
>>> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
>>> ---
>>> doc/guides/nics/dpaa2.rst | 3 +--
>>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>>
>>> diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
>>> index 7d7a6c5..46225b6 100644
>>> --- a/doc/guides/nics/dpaa2.rst
>>> +++ b/doc/guides/nics/dpaa2.rst
>>> @@ -441,8 +441,7 @@ compatible board:
>>>
>>> 1. **ARM 64 Tool Chain**
>>>
>>> - For example, the *aarch64* Linaro Toolchain, which can be obtained from
>>> - `here <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.
>>> + For example, the `*aarch64* Linaro Toolchain <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.
>>>
>>> 2. **Linux Kernel**
>>>
>>>
>>
>> I am not sure how to specific in patch that it applies on dpdk-net-next
>> in response to [1].
>
> I don't know either :), but thanks for letting know, I will check it.
I confirm this fixes the documentation warning, patch squashed into
relevant commit (17a4c3c16f5c)
>
>>
>> [1] http://dpdk.org/ml/archives/dev/2017-March/061335.html
>>
>
next prev parent reply other threads:[~2017-03-27 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 9:55 Shreyansh Jain
2017-03-27 9:57 ` Shreyansh Jain
2017-03-27 9:57 ` Ferruh Yigit
2017-03-27 11:12 ` Ferruh Yigit [this message]
2017-03-27 11:22 ` Mcnamara, John
2017-03-27 10:16 ` Mcnamara, John
2017-03-27 10:31 ` Mcnamara, John
2017-03-27 10:54 ` Shreyansh Jain
2017-03-27 10:45 ` Shreyansh Jain
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=df16cb56-62ff-bba6-8d17-119c51177c92@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=john.mcnamara@intel.com \
--cc=shreyansh.jain@nxp.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).