From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Helin Zhang <helin.zhang@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] compile fixes on ICC and clang
Date: Tue, 19 May 2015 10:25:29 +0900 [thread overview]
Message-ID: <555A9109.70105@igel.co.jp> (raw)
In-Reply-To: <1431961409-22252-1-git-send-email-helin.zhang@intel.com>
On 2015/05/19 0:03, Helin Zhang wrote:
> Compile warnings on ICC and clang can be found, and treated as errors.
> Disabling those warnings forcedly can fix them.
>
> v2 changes:
> Added the fix for the compile error on clang.
>
> Helin Zhang (2):
> i40e: compile fix on ICC 13.0.0
> i40e: compile fix on clang 3.3
>
> lib/librte_pmd_i40e/Makefile | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
Acked-by: Tetsuya Mukawa <mukawa@igel.co.jp>
prev parent reply other threads:[~2015-05-19 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 13:52 [dpdk-dev] [PATCH] i40e: compile fix on ICC 13.0.0 Helin Zhang
2015-05-18 15:03 ` [dpdk-dev] [PATCH v2 0/2] compile fixes on ICC and clang Helin Zhang
2015-05-18 15:03 ` [dpdk-dev] [PATCH v2 1/2] i40e/base: compile fix on ICC 13.0.0 Helin Zhang
2015-05-18 15:11 ` Bruce Richardson
2015-05-18 15:13 ` Bruce Richardson
2015-05-18 15:03 ` [dpdk-dev] [PATCH v2 2/2] i40e/base: compile fix on clang 3.3 Helin Zhang
2015-05-18 15:11 ` Bruce Richardson
2015-05-18 15:40 ` [dpdk-dev] [PATCH v3 0/2] fix compile with ICC and clang Helin Zhang
2015-05-18 15:40 ` [dpdk-dev] [PATCH v3 1/2] i40e/base: fix compile with ICC 13.0.0 Helin Zhang
2015-05-18 15:40 ` [dpdk-dev] [PATCH v3 2/2] i40e/base: fix compile with clang 3.3 Helin Zhang
2015-05-18 15:43 ` [dpdk-dev] [PATCH v3 0/2] fix compile with ICC and clang Bruce Richardson
2015-05-19 10:32 ` Thomas Monjalon
2015-05-19 14:12 ` Zhang, Helin
2015-05-19 1:25 ` Tetsuya Mukawa [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=555A9109.70105@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=dev@dpdk.org \
--cc=helin.zhang@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 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).