From: "Legacy, Allain" <Allain.Legacy@windriver.com>
To: "YIGIT, FERRUH" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] config: compile avp driver only on intel 64 bit
Date: Tue, 4 Apr 2017 17:17:03 +0000 [thread overview]
Message-ID: <70A7408C6E1BFB41B192A929744D8523969019F1@ALA-MBC.corp.ad.wrs.com> (raw)
In-Reply-To: <4712ffa9-b81c-bdef-ccc0-ae508d5b327d@intel.com>
> -----Original Message-----
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Tuesday, April 04, 2017 1:12 PM
<...>
>
> Right now compiler config files only have compiler and architecture configs,
> although it is OK to update them, to be consistent with what other PMDs did,
> what do you think:
>
> Keep AVP config enabled in "common_linuxapp"
>
> Disable AVP in following configs:
> defconfig_arm64-armv8a-linuxapp-gcc
> defconfig_arm-armv7a-linuxapp-gcc
> defconfig_ppc_64-power8-linuxapp-gcc
If that is your preference I can update the patch but either way a compiler config file is going to be changed. I did it the current way so that if a new architecture came along that they would not need to know to set AVP=n in their file.
Do you still want me to align to your suggestion?
next prev parent reply other threads:[~2017-04-04 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 16:36 Allain Legacy
2017-04-04 17:12 ` Ferruh Yigit
2017-04-04 17:17 ` Legacy, Allain [this message]
2017-04-04 17:20 ` Ferruh Yigit
2017-04-05 8:23 ` Bruce Richardson
2017-04-05 8:58 ` Thomas Monjalon
2017-04-05 10:08 ` Ferruh Yigit
2017-04-04 17:37 ` [dpdk-dev] [PATCH v2] " Allain Legacy
2017-04-07 11:13 ` Ferruh Yigit
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=70A7408C6E1BFB41B192A929744D8523969019F1@ALA-MBC.corp.ad.wrs.com \
--to=allain.legacy@windriver.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).