DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
	"Maxime Coquelin" <maxime.coquelin@redhat.com>,
	dpdk-techboard <techboard@dpdk.org>,
	"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
	"Christian Koue Muf" <ckm@napatech.com>,
	fengchengwen@huawei.com
Cc: Nathan Southern <nsouthern@linuxfoundation.org>, dev@dpdk.org
Subject: Re: [ADDENDUM] Technical board meeting agenda for 2023-09-20
Date: Wed, 20 Sep 2023 10:57:23 +0100	[thread overview]
Message-ID: <4c1aa6a8-bcc0-4073-9a17-6f4c7fb9cb7c@amd.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D87BD8@smartserver.smartshare.dk>

On 9/19/2023 2:53 PM, Morten Brørup wrote:
>> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
>> Sent: Tuesday, 19 September 2023 11.51
>>
>> Dear community,
>>
>> One topic was missed to be added to tomorrow's meeting agenda:
>>
>> On 9/18/23 22:20, Maxime Coquelin wrote:
>>> Dear DPDK community,
>>>
>>> Following topics are planned to be discussed at the next Technical board
>>> meeting, which will take place on Sept. 20th @3PM UTC:
>> 0- Event dispatcher library inclusion
>>
>>>   1- Memarea library inclusion
>>>   2- Power management brainstorming
>>>   3- Bugzilla maintenance: request for volunteers
>>>   4- Process to add new drivers
> 
> Christian Muf from Napatech will be joining the meeting for the new driver process discussion.
> 
> I suppose Ferruh will be joining for this discussion too.
> 

I explained my rationale in the mail list, let me share the link, it may
save time in the meeting:

https://mails.dpdk.org/archives/dev/2023-September/276671.html

>>>
>>> The order the topics will be discussed may change based on their
>>> priority/urgency. Some topics might have to be postponed to the
>>> following meeting if time does not allow to cover them.
>>>
>>> If time permits, below recurring items will be checked:
>>>   - Security process
>>>   - Community Lab
>>>   - Doc maintenance
>>>   - Bugzilla status
>>>   - Examples to drop or move
> 
> Please note the meeting URL is no longer Jitsi, but LFX Zoom:
> https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efeb
> 
> 


  reply	other threads:[~2023-09-20  9:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 20:20 Maxime Coquelin
2023-09-19  9:51 ` [ADDENDUM] " Maxime Coquelin
2023-09-19 13:53   ` Morten Brørup
2023-09-20  9:57     ` Ferruh Yigit [this message]
2023-10-08  1:04 ` fengchengwen

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=4c1aa6a8-bcc0-4073-9a17-6f4c7fb9cb7c@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=ckm@napatech.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mb@smartsharesystems.com \
    --cc=nsouthern@linuxfoundation.org \
    --cc=techboard@dpdk.org \
    /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).