From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhang, Ke1X" <ke1x.zhang@intel.com>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Ke1X" <ke1x.zhang@intel.com>
Subject: RE: [PATCH v2 0/1] fix Rx queue interrupt setting
Date: Fri, 20 May 2022 02:51:48 +0000 [thread overview]
Message-ID: <DM4PR11MB5994101601F98E6B0C974BA1D7D39@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220520023936.259286-1-ke1x.zhang@intel.com>
> -----Original Message-----
> From: Ke Zhang <ke1x.zhang@intel.com>
> Sent: Friday, May 20, 2022 10:40 AM
> To: Li, Xiaoyun <xiaoyun.li@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>; dev@dpdk.org
> Cc: Zhang, Ke1X <ke1x.zhang@intel.com>
> Subject: [PATCH v2 0/1] fix Rx queue interrupt setting
>
> v2:
> Add more explanation what's the issue and how we fix this issue in commit log.
For single patch, no need a separate change lot, it should be combined with the patch.
>
> Ke Zhang (1):
> net/iavf: fix Rx queue interrupt setting
>
> drivers/net/iavf/iavf_ethdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --
> 2.25.1
next prev parent reply other threads:[~2022-05-20 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:36 [PATCH] net/iavf: when E810 VF interrupt disable, only receive 4 packets once, fix 4 to 1 Ke Zhang
2022-05-19 9:29 ` [PATCH] net/iavf: fix iavf crashed on dev_stop when running in multi-process mode Ke Zhang
2022-05-19 9:30 ` [PATCH v2] net/iavf: fix Rx queue interrupt setting Ke Zhang
2022-05-19 9:56 ` Zhang, Qi Z
2022-05-20 2:39 ` [PATCH v2 0/1] " Ke Zhang
2022-05-20 2:39 ` [PATCH v2 1/1] net/iavf: " Ke Zhang
2022-05-20 2:51 ` Zhang, Qi Z [this message]
2022-05-20 3:00 ` [PATCH v2] " Ke Zhang
2022-05-20 3:15 ` Zhang, Qi Z
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=DM4PR11MB5994101601F98E6B0C974BA1D7D39@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=ke1x.zhang@intel.com \
--cc=xiaoyun.li@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).