From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yunjian Wang <wangyunjian@huawei.com>, <dev@dpdk.org>
Cc: <jingjing.wu@intel.com>, <beilei.xing@intel.com>,
<haiyue.wang@intel.com>, <jiawenwu@trustnetic.com>,
<jianwang@trustnetic.com>, <dingxiaoxiong@huawei.com>,
<huangshaozhang@huawei.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] fixes for ixgbe/txgbe/iavf
Date: Tue, 15 Feb 2022 14:27:58 +0000 [thread overview]
Message-ID: <f468a13d-8ba8-3b5f-dded-601dc02a085b@intel.com> (raw)
In-Reply-To: <cover.1644927269.git.wangyunjian@huawei.com>
On 2/15/2022 1:01 PM, Yunjian Wang wrote:
> This series include three fixes patches for ixgbe/txgbe/iavf.
> ---
> v2:
> * update patch 1/3 code styles suggested by Haiyue Wang
>
> Yunjian Wang (3):
> net/ixgbe: set pointer to NULL after free
> net/txgbe: set pointer to NULL after free
> net/iavf: set pointer to NULL after free
>
For series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2022-02-15 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 10:24 [dpdk-dev] [PATCH " Yunjian Wang
2022-02-15 10:24 ` [dpdk-dev] [PATCH 1/3] net/ixgbe: set pointer to NULL after free Yunjian Wang
2022-02-15 12:00 ` Wang, Haiyue
2022-02-15 10:24 ` [dpdk-dev] [PATCH 2/3] net/txgbe: " Yunjian Wang
2022-02-15 10:25 ` [dpdk-dev] [PATCH 3/3] net/iavf: " Yunjian Wang
2022-02-15 12:02 ` Wang, Haiyue
2022-02-15 12:10 ` wangyunjian
2022-02-15 13:01 ` [dpdk-dev] [PATCH v2 0/3] fixes for ixgbe/txgbe/iavf Yunjian Wang
2022-02-15 13:01 ` [dpdk-dev] [PATCH v2 1/3] net/ixgbe: set pointer to NULL after free Yunjian Wang
2022-02-15 13:02 ` [dpdk-dev] [PATCH v2 2/3] net/txgbe: " Yunjian Wang
2022-02-15 13:02 ` [dpdk-dev] [PATCH v2 3/3] net/iavf: " Yunjian Wang
2022-02-15 14:27 ` Ferruh Yigit [this message]
2022-02-16 14:17 ` [dpdk-dev] [PATCH v2 0/3] fixes for ixgbe/txgbe/iavf Ferruh Yigit
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=f468a13d-8ba8-3b5f-dded-601dc02a085b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=dingxiaoxiong@huawei.com \
--cc=haiyue.wang@intel.com \
--cc=huangshaozhang@huawei.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=jingjing.wu@intel.com \
--cc=wangyunjian@huawei.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).