From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: Chengwen Feng <fengchengwen@huawei.com>, <thomas@monjalon.net>,
<ferruh.yigit@intel.com>, <andrew.rybchenko@oktetlabs.ru>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: modify comment of INTR RESET event
Date: Wed, 11 Aug 2021 12:45:01 +0530 [thread overview]
Message-ID: <cd5af5da-3b93-50a5-90da-da1bc890fca0@intel.com> (raw)
In-Reply-To: <1627281811-45185-1-git-send-email-fengchengwen@huawei.com>
Hi Chengwen,
On 7/26/2021 12:13 PM, Chengwen Feng wrote:
> According to the definition of rte_eth_dev_reset(), the
> RTE_ETH_EVENT_INTR_RESET event could also use when PF resets.
>
> This patch modifies the comment of RTE_ETH_EVENT_INTR_RESET event, so
> that it could use in all resets.
>
> Signed-off-by: Chengwen Feng<fengchengwen@huawei.com>
> ---
> lib/ethdev/rte_ethdev.h | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
> index d2b27c3..e6646a6 100644
> --- a/lib/ethdev/rte_ethdev.h
> +++ b/lib/ethdev/rte_ethdev.h
> @@ -3499,8 +3499,7 @@ enum rte_eth_event_type {
> RTE_ETH_EVENT_INTR_LSC, /**< lsc interrupt event */
> RTE_ETH_EVENT_QUEUE_STATE,
> /**< queue state event (enabled/disabled) */
> - RTE_ETH_EVENT_INTR_RESET,
> - /**< reset interrupt event, sent to VF on PF reset */
> + RTE_ETH_EVENT_INTR_RESET, /**< reset interrupt event */
> RTE_ETH_EVENT_VF_MBOX, /**< message from the VF received by PF */
> RTE_ETH_EVENT_MACSEC, /**< MACsec offload related event */
> RTE_ETH_EVENT_INTR_RMV, /**< device removal event */
Acked-by: Aman Deep Singh <aman.deep.singh@intel.com>
next prev parent reply other threads:[~2021-08-11 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 6:43 Chengwen Feng
2021-08-11 7:15 ` Singh, Aman Deep [this message]
2021-09-27 16:19 ` Ferruh Yigit
2022-01-15 6:44 ` Kalesh Anakkur Purayil
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=cd5af5da-3b93-50a5-90da-da1bc890fca0@intel.com \
--to=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).