From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Singh, Aman Deep" <aman.deep.singh@intel.com>,
okaya@kernel.org, Yuying Zhang <yuying.zhang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] testpmd: unregister event callback
Date: Wed, 27 Sep 2023 18:52:22 +0100 [thread overview]
Message-ID: <e464e143-435e-4937-b52a-5fad761c4233@amd.com> (raw)
In-Reply-To: <c48b9b42-3ae9-1c51-ae75-358507928e4e@intel.com>
On 9/26/2023 4:50 PM, Singh, Aman Deep wrote:
>
> On 9/15/2023 9:56 AM, okaya@kernel.org wrote:
>> From: Sinan Kaya <okaya@kernel.org>
>
> Header format doesn't requires to add "From: "
> as author "Signed-off" is already present.
>
>>
>> Cleanup event registry during shutdown to prevent memory
>> leaks.
>>
>> Signed-off-by: Sinan Kaya <okaya@kernel.org>
>
> Acked-by: Aman Singh <aman.deep.singh@intel.com>
>
Applied to dpdk-next-net/main, thanks.
(patch title and .mailmap updated while merging)
prev parent reply other threads:[~2023-09-27 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 4:26 okaya
2023-09-26 15:50 ` Singh, Aman Deep
2023-09-27 17:52 ` 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=e464e143-435e-4937-b52a-5fad761c4233@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=okaya@kernel.org \
--cc=yuying.zhang@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).