From: "Yuan, DukaiX" <dukaix.yuan@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>,
"Jianfeng Tan" <jianfeng.tan@intel.com>,
Junjie Chen <junjie.j.chen@intel.com>,
"Hyong Youb Kim" <hyonkim@cisco.com>,
Harman Kalra <hkalra@marvell.com>
Subject: RE: [PATCH 3/3] net/vhost: fix Rx interrupt
Date: Mon, 13 Mar 2023 02:39:35 +0000 [thread overview]
Message-ID: <CH2PR11MB4487417787C539CA32129844E8B99@CH2PR11MB4487.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230309123752.2237828-4-david.marchand@redhat.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: 2023年3月9日 20:38
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Maxime Coquelin <maxime.coquelin@redhat.com>;
> Xia, Chenbo <chenbo.xia@intel.com>; Jianfeng Tan
> <jianfeng.tan@intel.com>; Junjie Chen <junjie.j.chen@intel.com>; Hyong
> Youb Kim <hyonkim@cisco.com>; Harman Kalra <hkalra@marvell.com>
> Subject: [PATCH 3/3] net/vhost: fix Rx interrupt
>
Tested-by: Dukai Yuan<dukaix.yuan@intel.com>
next prev parent reply other threads:[~2023-03-13 2:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 12:37 [PATCH 0/3] net/vhost pmd fixes for Rx interrupts David Marchand
2023-03-09 12:37 ` [PATCH 1/3] net/vhost: add missing newline in logs David Marchand
2023-03-10 3:16 ` Xia, Chenbo
2023-03-09 12:37 ` [PATCH 2/3] net/vhost: fix leak in interrupt handle setup David Marchand
2023-03-10 3:16 ` Xia, Chenbo
2023-03-09 12:37 ` [PATCH 3/3] net/vhost: fix Rx interrupt David Marchand
2023-03-10 7:35 ` Xia, Chenbo
2023-03-13 2:39 ` Yuan, DukaiX [this message]
2023-03-14 8:59 ` David Marchand
2023-03-14 11:07 ` Maxime Coquelin
2023-03-16 14:47 ` [PATCH 0/3] net/vhost pmd fixes for Rx interrupts Maxime Coquelin
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=CH2PR11MB4487417787C539CA32129844E8B99@CH2PR11MB4487.namprd11.prod.outlook.com \
--to=dukaix.yuan@intel.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=hyonkim@cisco.com \
--cc=jianfeng.tan@intel.com \
--cc=junjie.j.chen@intel.com \
--cc=maxime.coquelin@redhat.com \
--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).