From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>,
"Carrillo, Erik G" <erik.g.carrillo@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v4 2/4] event/sw: report periodic event timer capability
Date: Tue, 6 Sep 2022 08:10:02 +0000 [thread overview]
Message-ID: <BN0PR11MB571298CA29AEC93D11F34743D77E9@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220812160734.287123-1-s.v.naga.harish.k@intel.com>
> -----Original Message-----
> From: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
> Sent: Friday, August 12, 2022 5:08 PM
> To: Carrillo, Erik G <erik.g.carrillo@intel.com>; jerinj@marvell.com; Van Haaren,
> Harry <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org
> Subject: [PATCH v4 2/4] event/sw: report periodic event timer capability
>
> update the software eventdev pmd timer_adapter_caps_get
> callback function to report the support of periodic
> event timer capability
>
> Signed-off-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>
Thanks for explaining how things work on the v2 & follow-up reworks;
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
next prev parent reply other threads:[~2022-09-06 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 16:26 [PATCH " Naga Harish K S V
2022-08-05 12:00 ` Van Haaren, Harry
2022-08-10 11:01 ` Naga Harish K, S V
2022-08-10 7:09 ` [PATCH v2 " Naga Harish K S V
2022-08-10 20:52 ` Carrillo, Erik G
2022-08-11 15:33 ` Van Haaren, Harry
2022-08-11 15:44 ` Naga Harish K, S V
2022-08-11 15:37 ` [PATCH v3 " Naga Harish K S V
2022-08-12 16:07 ` [PATCH v4 " Naga Harish K S V
2022-09-06 8:10 ` Van Haaren, Harry [this message]
2022-09-09 5:33 ` Naga Harish K, S V
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=BN0PR11MB571298CA29AEC93D11F34743D77E9@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=jerinj@marvell.com \
--cc=s.v.naga.harish.k@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).