From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Mingxia Liu <mingxia.liu@intel.com>
Cc: jingjing.wu@intel.com, beilei.xing@intel.com, dev@dpdk.org
Subject: Re: [PATCH] net/idpf: fix a compiler issue about virtchnl opcode
Date: Thu, 9 Mar 2023 12:10:01 +0000 [thread overview]
Message-ID: <6a98b602-0342-2cde-3aba-ebc0135519d7@amd.com> (raw)
In-Reply-To: <20230309115219.278021-1-mingxia.liu@intel.com>
On 3/9/2023 11:52 AM, Mingxia Liu wrote:
> Comparing an enum virtchnl_ops variable with VIRTCHNL2_OP_EVENT
> will cause a compiler issue, as VIRTCHNL2_OP_EVENT is not included
> in enum virtchnl_ops. And the PMD uses virtual msg opcodes prefixed
> with virtchnl2 or VIRTCHNL2.
>
> Fixes: 78049b3dc7e6 ("net/idpf: add alarm to handle virtual channel message")
>
Fixes: d633a4859c98 ("net/idpf: add alarm to handle virtual channel
message")
> Signed-off-by: Mingxia Liu <mingxia.liu@intel.com>
Reported-by: Raslan Darawsheh <rasland@nvidia.com>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-03-09 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 11:52 Mingxia Liu
2023-03-09 12:10 ` 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=6a98b602-0342-2cde-3aba-ebc0135519d7@amd.com \
--to=ferruh.yigit@amd.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=mingxia.liu@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).