From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ed Czeck <ed.czeck@atomicrules.com>,
dev@dpdk.org, bruce.richardson@intel.com
Cc: fengchengwen@huawei.com, shepard.siegel@atomicrules.com,
john.miller@atomicrules.com
Subject: Re: [dpdk-dev] [PATCH 1/2] net/ark: fix bug introduced during thread name addition
Date: Tue, 11 May 2021 23:50:01 +0100 [thread overview]
Message-ID: <c5d01ce9-0b73-4c6e-ff01-f4854c66c8ef@intel.com> (raw)
In-Reply-To: <a8ac1401-778b-8b58-65e4-8a4af27af410@intel.com>
On 5/11/2021 11:48 PM, Ferruh Yigit wrote:
> On 5/11/2021 9:58 PM, Ed Czeck wrote:
>> Fixes: fdefe038eb9b ("net/ark: set generator delay thread name")
>> Cc: fengchengwen@huawei.com
>>
>> Signed-off-by: Ed Czeck <ed.czeck@atomicrules.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Applied to dpdk-next-net/main, thanks.
> (changed the patch title and added a commit log, please check)
>
The patch title is 1/2, is there a missing patch 2/2?
next prev parent reply other threads:[~2021-05-11 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 20:58 Ed Czeck
2021-05-11 22:48 ` Ferruh Yigit
2021-05-11 22:50 ` Ferruh Yigit [this message]
2021-05-11 23:01 ` Ed Czeck
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=c5d01ce9-0b73-4c6e-ff01-f4854c66c8ef@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=fengchengwen@huawei.com \
--cc=john.miller@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).