From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ankur Dwivedi <adwivedi@marvell.com>, dev@dpdk.org
Cc: weiyuanx.li@intel.com, jerinj@marvell.com,
david.marchand@redhat.com, thomas@monjalon.net,
yux.jiang@intel.com, dukaix.yuan@intel.com
Subject: Re: [PATCH v2 0/2] bug fix in ethdev trace
Date: Fri, 3 Mar 2023 13:39:19 +0000 [thread overview]
Message-ID: <224797be-f5b1-67d2-aef6-39f631b4d4c4@amd.com> (raw)
In-Reply-To: <20230303113137.2745570-1-adwivedi@marvell.com>
On 3/3/2023 11:31 AM, Ankur Dwivedi wrote:
> The first patch in this series adds fix for bug and coverity.
> The second patch makes change to pass structure pointer instead of the
> structure value, to avoid 64 bytes copy in function call stack for
> rte_eth_trace_xstats_get_names.
>
> v2:
> - Removed null pointer reference in rte_eth_trace_read_clock and
> rte_flow_trace_create.
> - Added Ack by Ferruh in patch (2/2).
>
> Ankur Dwivedi (2):
> ethdev: fix null pointer dereference
> ethdev: pass structure pointer
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-03-03 13:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 12:30 [PATCH v1 " Ankur Dwivedi
2023-02-23 12:30 ` [PATCH v1 1/2] ethdev: fix null pointer dereference Ankur Dwivedi
2023-02-28 11:04 ` Ferruh Yigit
2023-02-28 11:29 ` David Marchand
2023-02-28 12:46 ` Ferruh Yigit
2023-02-28 13:17 ` Jerin Jacob
2023-02-28 13:39 ` Ferruh Yigit
2023-02-28 15:01 ` Ferruh Yigit
2023-02-28 15:40 ` [EXT] " Ankur Dwivedi
2023-02-28 16:08 ` Ferruh Yigit
2023-02-28 16:27 ` Ferruh Yigit
2023-03-02 9:58 ` Ferruh Yigit
2023-03-02 16:49 ` Ankur Dwivedi
2023-02-23 12:30 ` [PATCH v1 2/2] ethdev: pass structure pointer Ankur Dwivedi
2023-02-28 15:01 ` Ferruh Yigit
2023-03-03 11:31 ` [PATCH v2 0/2] bug fix in ethdev trace Ankur Dwivedi
2023-03-03 11:31 ` [PATCH v2 1/2] ethdev: fix null pointer dereference Ankur Dwivedi
2023-03-03 13:38 ` Ferruh Yigit
2023-03-03 11:31 ` [PATCH v2 2/2] ethdev: pass structure pointer Ankur Dwivedi
2023-03-03 13:39 ` 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=224797be-f5b1-67d2-aef6-39f631b4d4c4@amd.com \
--to=ferruh.yigit@amd.com \
--cc=adwivedi@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dukaix.yuan@intel.com \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
--cc=weiyuanx.li@intel.com \
--cc=yux.jiang@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).