From: Alexander Kozyrev <akozyrev@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>, Matan Azrad <matan@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"adwivedi@marvell.com" <adwivedi@marvell.com>
Subject: RE: [PATCH] ethdev: fix asynchronous destroy and push tracepoints
Date: Tue, 23 May 2023 17:37:54 +0000 [thread overview]
Message-ID: <MW2PR12MB24129C9C2EC8E2A773B6EAE5AF409@MW2PR12MB2412.namprd12.prod.outlook.com> (raw)
In-Reply-To: <15464a44-84c6-1b84-9c80-a6c62c43b85a@amd.com>
> Patch doesn't apply cleanly because it can't find
> 'rte_flow_trace_async_update', is there a dependency?
Fixed in v2. The patch was based on my "update rule" commit.
next prev parent reply other threads:[~2023-05-23 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 21:59 Alexander Kozyrev
2023-05-19 5:21 ` [EXT] " Ankur Dwivedi
2023-05-21 19:09 ` Ori Kam
2023-05-19 9:00 ` Ferruh Yigit
2023-05-23 17:37 ` Alexander Kozyrev [this message]
2023-05-23 17:39 ` [PATCH v2] " Alexander Kozyrev
2023-05-24 9:51 ` 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=MW2PR12MB24129C9C2EC8E2A773B6EAE5AF409@MW2PR12MB2412.namprd12.prod.outlook.com \
--to=akozyrev@nvidia.com \
--cc=adwivedi@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.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).