From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com
Subject: Re: [PATCH v2 0/3] enhance NFP service framework
Date: Thu, 8 Feb 2024 13:58:44 +0000 [thread overview]
Message-ID: <d6b8c564-d337-46f1-bd5a-653a42632974@amd.com> (raw)
In-Reply-To: <20240202030415.739638-1-chaoyong.he@corigine.com>
On 2/2/2024 3:04 AM, Chaoyong He wrote:
> Make multiple devices can use single core to run services for
> flower firmware.
> Also add synchronize module and service module to support it.
>
> ---
> v2:
> * Merge the last commit of v1 into the second commit.
> ---
>
> Long Wu (3):
> net/nfp: add synchronize module
> net/nfp: create new service code related files
> net/nfp: flower driver uses one service core
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-02-08 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 9:25 [PATCH 0/4] " Chaoyong He
2024-01-24 9:25 ` [PATCH 1/4] net/nfp: add synchronize module Chaoyong He
2024-01-24 9:25 ` [PATCH 2/4] net/nfp: create new service code related files Chaoyong He
2024-01-24 9:25 ` [PATCH 3/4] net/nfp: flower driver uses one service core Chaoyong He
2024-01-24 9:25 ` [PATCH 4/4] net/nfp: fix stop cpp service problem Chaoyong He
2024-01-30 12:07 ` Ferruh Yigit
2024-01-30 12:17 ` Kevin Traynor
2024-02-02 3:04 ` [PATCH v2 0/3] enhance NFP service framework Chaoyong He
2024-02-02 3:04 ` [PATCH v2 1/3] net/nfp: add synchronize module Chaoyong He
2024-02-02 3:04 ` [PATCH v2 2/3] net/nfp: create new service code related files Chaoyong He
2024-02-02 3:04 ` [PATCH v2 3/3] net/nfp: flower driver uses one service core Chaoyong He
2024-02-06 15:17 ` [PATCH v2 0/3] enhance NFP service framework Ferruh Yigit
2024-02-08 9:52 ` Chaoyong He
2024-02-08 13:58 ` 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=d6b8c564-d337-46f1-bd5a-653a42632974@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=oss-drivers@corigine.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).