From: fengchengwen <fengchengwen@huawei.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Marchand, David" <david.marchand@redhat.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: DPDK Release Status Meeting 2023-12-14
Date: Fri, 15 Dec 2023 17:34:28 +0800 [thread overview]
Message-ID: <e038df19-c5c6-143a-1c04-42e7757f5dbb@huawei.com> (raw)
In-Reply-To: <d3eee1be-0181-4ca5-9af0-95833d779344@amd.com>
Hi Ferruh,
On 2023/12/15 17:24, Ferruh Yigit wrote:
> On 12/15/2023 12:43 AM, fengchengwen wrote:
>> Hi TB,
>>
>> On 2023/12/14 21:39, Mcnamara, John wrote:
>>> Release status meeting minutes 2023-12-14
>>>
>>> =========================================
>>>
>>
>> ...
>>
>>>
>>> * main
>>>
>>> * V1 date moved to December 29th
>>>
>>> * New branch mirroring to GitHub to reduce load on git.dpdk.org.
>>>
>>> * Request for Roadmaps: https://core.dpdk.org/roadmap/
>>>
>>> * Looking for a new maintainer for the DMA device performance tool.
>>
>> If could, I'll be the new maintainer, and I already sent the commit.
>>
>
> Akhil highlighted that Gowrishankar already volunteered some time ago
> [1], which I missed.
I also missed.
> I assume that patch is not merged because original maintainer not acked
> it, perhaps original maintainer is not following mail list.
That's OK, we both want make DPDK better.
Thanks.
>
>
> [1]
> https://patchwork.dpdk.org/project/dpdk/patch/1d1e3d699f2e47a7b822144df2c7a074c889a0a3.1698375266.git.gmuthukrishn@marvell.com/
>
> .
>
prev parent reply other threads:[~2023-12-15 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 13:39 Mcnamara, John
2023-12-15 0:43 ` fengchengwen
2023-12-15 9:24 ` Ferruh Yigit
2023-12-15 9:34 ` fengchengwen [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=e038df19-c5c6-143a-1c04-42e7757f5dbb@huawei.com \
--to=fengchengwen@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/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).