DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wang, Xiao W" <xiao.w.wang@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/fm10k: fix non-x86 build
Date: Wed, 19 Feb 2020 17:33:42 +0000	[thread overview]
Message-ID: <55e9801a-85fc-73f4-6356-3867fb00352d@intel.com> (raw)
In-Reply-To: <B7F2E978279D1D49A3034B7786DACF407D4135B9@SHSMSX103.ccr.corp.intel.com>

On 2/19/2020 2:31 PM, Wang, Xiao W wrote:

> 
>> -----Original Message-----
>> From: Yigit, Ferruh <ferruh.yigit@intel.com>
>> Sent: Wednesday, February 19, 2020 10:17 PM
>> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Wang, Xiao W
>> <xiao.w.wang@intel.com>; Chen Jing D(Mark) <jing.d.chen@intel.com>
>> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; stable@dpdk.org
>> Subject: [PATCH] net/fm10k: fix non-x86 build
>>
>> 'fm10k_rxtx_vec.c' is SSE vector instructions implementation and should
>> be compiled only for x86.
>>
>> The vector PMD support controlled by
>> 'CONFIG_RTE_LIBRTE_FM10K_INC_VECTOR' config option, but it is enabled
>> by
>> default, safer to add x86 checks too.
>>
>> Fixes: 10eb9ce8dccd ("fm10k: allow to disable vector driver")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Acked-by: Xiao Wang <xiao.w.wang@intel.com>
> 

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2020-02-19 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 14:16 Ferruh Yigit
2020-02-19 14:31 ` Wang, Xiao W
2020-02-19 17:33   ` Ferruh Yigit [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=55e9801a-85fc-73f4-6356-3867fb00352d@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=xiao.w.wang@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).