From: Jerin Jacob <jerinj@marvell.com>
To: Luka Jankovic <luka.jankovic@ericsson.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Pavan Nikhilesh Bhagavatula" <pbhagavatula@marvell.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: RE: [PATCH v9 0/3] eventdev: atomic tests to test-eventdev app
Date: Thu, 6 Mar 2025 08:27:17 +0000 [thread overview]
Message-ID: <BY3PR18MB4785C9D2BC77CE2B66CE5AD6C8CA2@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <818c4278b785cd4d0ae716602a6d6044900683ba.camel@ericsson.com>
> -----Original Message-----
> From: Luka Jankovic <luka.jankovic@ericsson.com>
> Sent: Thursday, March 6, 2025 1:46 PM
> To: Luka Jankovic <luka.jankovic@ericsson.com>
> Cc: dev@dpdk.org; Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>;
> Jerin Jacob <jerinj@marvell.com>; Mattias Rönnblom
> <mattias.ronnblom@ericsson.com>
> Subject: [EXTERNAL] Re: [PATCH v9 0/3] eventdev: atomic tests to test-eventdev
> app
>
> I accidentally sent the last version (v9) with an incorrect git name, but the
> commits are signed correctly. Will this be an issue or should I upload a new
> version with the correct name?
Please resend
>
> I accidentally sent the last version (v9) with an incorrect git name, but the
> commits are signed correctly. Will this be an issue or should I upload a new
> version with the correct name?
next prev parent reply other threads:[~2025-03-06 8:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 14:48 [RFC v2 1/1] eventdev: add atomic queue " Luka Jankovic
2024-12-23 11:16 ` Mattias Rönnblom
2025-01-09 10:22 ` Luka Jankovic
2025-01-13 9:04 ` [RFC v3 " ejnulak
2025-01-13 12:17 ` [RFC v4 " Luka Jankovic
2025-01-13 12:27 ` [EXTERNAL] " Jerin Jacob
2025-01-15 13:38 ` [RFC v5 1/2] " Luka Jankovic
2025-01-22 10:20 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-01-22 15:10 ` Luka Jankovic
2025-01-24 9:59 ` [RFC PATCH v6 " Luka Jankovic
2025-02-04 16:11 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-02-14 9:58 ` Luka Jankovic
2025-02-14 15:59 ` Pavan Nikhilesh Bhagavatula
2025-02-19 13:43 ` [RFC v7 0/4] eventdev: atomic tests " Luka Jankovic
2025-02-19 13:43 ` [RFC v7 1/4] eventdev: atomic common for " Luka Jankovic
2025-02-19 13:43 ` [RFC v7 2/4] eventdev: add atomic queue test to test-evnetdev app Luka Jankovic
2025-02-19 13:43 ` [RFC v7 3/4] eventdev: add atomic atq to test-eventdev app Luka Jankovic
2025-02-19 13:43 ` [RFC v7 4/4] eventdev: documentation for atomic queue and atomic atq tests Luka Jankovic
2025-03-02 11:30 ` [EXTERNAL] " Jerin Jacob
2025-02-20 9:13 ` [EXTERNAL] [RFC v7 0/4] eventdev: atomic tests to test-eventdev app Pavan Nikhilesh Bhagavatula
2025-03-05 12:52 ` [PATCH v8 0/3] " Luka Jankovic
2025-03-05 12:52 ` [PATCH] eventdev: atomic common for " Luka Jankovic
2025-03-05 12:52 ` [PATCH v8 2/3] eventdev: add atomic queue test to test-evnetdev app Luka Jankovic
2025-03-05 12:52 ` [PATCH v8 3/3] eventdev: add atomic atq to test-eventdev app Luka Jankovic
2025-03-05 14:12 ` [PATCH v9 0/3] eventdev: atomic tests " ejnulak
2025-03-05 14:12 ` [PATCH v9 1/3] eventdev: atomic common for " ejnulak
2025-03-05 14:12 ` [PATCH v9 2/3] eventdev: add atomic queue test to test-evnetdev app ejnulak
2025-03-05 14:12 ` [PATCH v9 3/3] eventdev: add atomic atq to test-eventdev app ejnulak
2025-03-06 3:01 ` Patrick Robb
2025-03-06 8:16 ` [PATCH v9 0/3] eventdev: atomic tests " Luka Jankovic
2025-03-06 8:27 ` Jerin Jacob [this message]
2025-03-06 8:49 ` [PATCH v10 " Luka Jankovic
2025-03-06 8:49 ` [PATCH v10 1/3] eventdev: atomic common for " Luka Jankovic
2025-03-06 8:49 ` [PATCH v10 2/3] eventdev: add atomic queue test to test-evnetdev app Luka Jankovic
2025-03-06 8:49 ` [PATCH v10 3/3] eventdev: add atomic atq to test-eventdev app Luka Jankovic
2025-01-24 9:59 ` [RFC PATCH v6 2/2] eventdev: documentation for atomic queue test Luka Jankovic
2025-01-15 13:38 ` [RFC v5 " Luka Jankovic
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=BY3PR18MB4785C9D2BC77CE2B66CE5AD6C8CA2@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=luka.jankovic@ericsson.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=pbhagavatula@marvell.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).