From: Alvin Zhang <alvinx.zhang@intel.com>
To: beilei.xing@intel.com, Ting.Xu@intel.com
Cc: dev@dpdk.org, Alvin Zhang <alvinx.zhang@intel.com>, stable@dpdk.org
Subject: [dpdk-dev] [PATCH v2 1/3] net/i40e: fix return status for unsupported VF message
Date: Tue, 11 May 2021 09:50:00 +0800 [thread overview]
Message-ID: <20210511015002.16644-1-alvinx.zhang@intel.com> (raw)
This patch modifies the return status for unsupported VF messages,
in order to make it the same as the return status of the kernel driver.
Fixes: 4861cde46116 ("i40e: new poll mode driver")
Cc: stable@dpdk.org
Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
---
drivers/net/i40e/i40e_pf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/i40e/i40e_pf.c b/drivers/net/i40e/i40e_pf.c
index 9804ed4..308da1b 100644
--- a/drivers/net/i40e/i40e_pf.c
+++ b/drivers/net/i40e/i40e_pf.c
@@ -1464,8 +1464,8 @@
*/
default:
PMD_DRV_LOG(ERR, "%u received, not supported", opcode);
- i40e_pf_host_send_msg_to_vf(vf, opcode, I40E_ERR_PARAM,
- NULL, 0);
+ i40e_pf_host_send_msg_to_vf(vf, opcode,
+ I40E_ERR_NOT_IMPLEMENTED, NULL, 0);
break;
}
--
1.8.3.1
next reply other threads:[~2021-05-11 1:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 1:50 Alvin Zhang [this message]
2021-05-11 1:50 ` [dpdk-dev] [PATCH v2 2/3] common/iavf: fix V-channel status Alvin Zhang
2021-05-11 1:50 ` [dpdk-dev] [PATCH v2 3/3] net/iavf: fix V-channel message status Alvin Zhang
2021-05-11 2:02 ` [dpdk-dev] [PATCH v3 1/3] net/i40e: fix return status for unsupported VF message Alvin Zhang
2021-05-11 2:02 ` [dpdk-dev] [PATCH v3 2/3] common/iavf: fix V-channel status Alvin Zhang
2021-05-11 2:40 ` Xing, Beilei
2021-05-11 2:02 ` [dpdk-dev] [PATCH v3 3/3] net/iavf: fix V-channel message status Alvin Zhang
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=20210511015002.16644-1-alvinx.zhang@intel.com \
--to=alvinx.zhang@intel.com \
--cc=Ting.Xu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).