From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Aaron Conole <aconole@redhat.com>,
dev@dpdk.org, techboard@dpdk.org,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
Akhil Goyal <gakhil@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: Minutes of Technical Board meeting 17-April-2024
Date: Fri, 3 May 2024 16:24:54 +0100 [thread overview]
Message-ID: <5d041a04-3df7-4d8f-a41b-bd19d7403f67@amd.com> (raw)
In-Reply-To: <f7to79nc86l.fsf@redhat.com>
On 5/3/2024 2:54 PM, Aaron Conole wrote:
> - Mykola has questions about submitting for a refactored PMD series
> - Answered some live, referred to the guides in the documentation
> as well.
> - Plan to send a simpler version of the PMD
> - Include any restrictions in docs
> - Trying to understand the deadlines as well for the PMD
> submissions
> - Drivers generally get merged in -RC2
> - Suggestion is to post patches early because reviews will take
> some time.
>
We are having questions around best practices to submit a new PMD and we
don't have a comprehensive documentation around it. And this is
sometimes causing frustration.
I assume one of the reasons related to the missing documentation is, it
is hard to come with generalized guidelines. But by time, as maintainers
we had formed some best practices in our mind and I believe they are
mature enough to document.
That is why I suggest forming a new workgroup with tree maintainers, and
work on documenting process or best practices to submit a new PMD. This
can be a time bound workgroup and task, like one quarter/release.
What do you think?
prev parent reply other threads:[~2024-05-03 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 13:54 Minutes of Technical Board meeting 17-April-2024 Aaron Conole
2024-05-03 15:24 ` 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=5d041a04-3df7-4d8f-a41b-bd19d7403f67@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=techboard@dpdk.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).