From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 03B10FA41 for ; Mon, 27 Mar 2017 11:57:25 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga105.fm.intel.com with ESMTP; 27 Mar 2017 02:57:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,231,1486454400"; d="scan'208";a="81357282" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.122]) ([10.237.220.122]) by fmsmga006.fm.intel.com with ESMTP; 27 Mar 2017 02:57:24 -0700 To: Shreyansh Jain References: <1490608518-27315-1-git-send-email-shreyansh.jain@nxp.com> Cc: hemant.agrawal@nxp.com, dev@dpdk.org, john.mcnamara@intel.com From: Ferruh Yigit Message-ID: <7137b742-c16e-82a2-2acd-2d052d5a2c26@intel.com> Date: Mon, 27 Mar 2017 10:57:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] doc: fix DPAA2 guide build warning X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 09:57:26 -0000 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 >> --- >> 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 `_. >> + For example, the `*aarch64* Linaro Toolchain `_. >> >> 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. > > [1] http://dpdk.org/ml/archives/dev/2017-March/061335.html >