DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, Rosen" <rosen.xu@intel.com>
To: "Huang, Wei" <wei.huang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"Zhang,  Qi Z" <qi.z.zhang@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Zhang, Tianfei" <tianfei.zhang@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: RE: [PATCH v1 4/4] raw/ifpga/base: fix port feature ID
Date: Tue, 18 Jan 2022 06:39:07 +0000	[thread overview]
Message-ID: <DM6PR11MB4252457BDE0CAFB58448752789589@DM6PR11MB4252.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220118031738.2059-5-wei.huang@intel.com>

Hi Wei,

Some issues of ci/iol-x86_64-unit-testing, pls check it. Thanks a lot.

Thanks,
Rosen

-----Original Message-----
From: Huang, Wei <wei.huang@intel.com> 
Sent: Tuesday, January 18, 2022 11:18 AM
To: dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
Cc: stable@dpdk.org; Zhang, Tianfei <tianfei.zhang@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Huang, Wei <wei.huang@intel.com>
Subject: [PATCH v1 4/4] raw/ifpga/base: fix port feature ID

Fix ID value of port features to match the definition from hardware.

Fixes: 473c88f9 ("drivers/raw: remove rawdev from directory names")

Signed-off-by: Wei Huang <wei.huang@intel.com>
---
 drivers/raw/ifpga/base/ifpga_defines.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/raw/ifpga/base/ifpga_defines.h b/drivers/raw/ifpga/base/ifpga_defines.h
index dca1518..8f62033 100644
--- a/drivers/raw/ifpga/base/ifpga_defines.h
+++ b/drivers/raw/ifpga/base/ifpga_defines.h
@@ -93,9 +93,9 @@ enum fpga_id_type {
 
 #define PORT_FEATURE_ID_HEADER FEATURE_ID_FIU_HEADER  #define PORT_FEATURE_ID_ERROR 0x10 -#define PORT_FEATURE_ID_UMSG 0x12 -#define PORT_FEATURE_ID_UINT 0x13 -#define PORT_FEATURE_ID_STP 0x14
+#define PORT_FEATURE_ID_UMSG 0x11
+#define PORT_FEATURE_ID_UINT 0x12
+#define PORT_FEATURE_ID_STP 0x13
 #define PORT_FEATURE_ID_UAFU FEATURE_ID_AFU
 
 /*
--
1.8.3.1


  reply	other threads:[~2022-01-18  6:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  3:17 [PATCH v1 0/4] Fix bugs found in raw/ifpga development for arrow creek Wei Huang
2022-01-18  3:17 ` [PATCH v1 1/4] raw/ifpga/base: fix SPI transaction Wei Huang
2022-01-18  3:17 ` [PATCH v1 2/4] raw/ifpga: fix pthread cannot join Wei Huang
2022-01-18  3:17 ` [PATCH v1 3/4] raw/ifpga: fix ifpga devices cleanup function Wei Huang
2022-01-18  3:17 ` [PATCH v1 4/4] raw/ifpga/base: fix port feature ID Wei Huang
2022-01-18  6:39   ` Xu, Rosen [this message]
2022-01-18  7:37 ` [PATCH v2 0/4] Fix bugs found in raw/ifpga development for arrow creek Wei Huang
2022-01-18  7:37   ` [PATCH v2 1/4] raw/ifpga/base: fix SPI transaction Wei Huang
2022-01-18  7:37   ` [PATCH v2 2/4] raw/ifpga: fix pthread cannot join Wei Huang
2022-01-18  7:37   ` [PATCH v2 3/4] raw/ifpga: fix ifpga devices cleanup function Wei Huang
2022-01-18  7:37   ` [PATCH v2 4/4] raw/ifpga/base: fix port feature ID Wei Huang

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=DM6PR11MB4252457BDE0CAFB58448752789589@DM6PR11MB4252.namprd11.prod.outlook.com \
    --to=rosen.xu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=tianfei.zhang@intel.com \
    --cc=wei.huang@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).