From: Jerin Jacob <jerinjacobk@gmail.com>
To: jerinj@marvell.com
Cc: dev@dpdk.org, thomas@monjalon.net, david.marchand@redhat.com,
ferruh.yigit@amd.com, techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: process for new library approval in principle
Date: Thu, 20 Jul 2023 12:03:51 +0530 [thread overview]
Message-ID: <CALBAE1O-aEEQTGjHFT9zn3OSoyU4S_dgHj57WdiSh7Cp=6-zQg@mail.gmail.com> (raw)
In-Reply-To: <20230518132139.1350234-1-jerinj@marvell.com>
On Thu, May 18, 2023 at 6:52 PM <jerinj@marvell.com> wrote:
>
> From: Jerin Jacob <jerinj@marvell.com>
>
> Based on techboard meeting[1] action item, defining the process for a
> new library approval in principle.
>
> [1]
> https://mails.dpdk.org/archives/dev/2023-January/260035.html
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> RFC..v1:
> - Fix the review comments by Konstantin, Keven, Thomas at
> http://patches.dpdk.org/project/dpdk/patch/20230213092616.3589932-1-jerinj@marvell.com/
Ping for review or merge
next prev parent reply other threads:[~2023-07-20 6:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 9:26 [dpdk-web] [RFC PATCH] process: " jerinj
2023-03-01 8:28 ` Jerin Jacob
2023-03-03 18:25 ` Thomas Monjalon
2023-03-15 13:47 ` Jerin Jacob
2023-03-30 12:48 ` Jerin Jacob
2023-04-17 13:33 ` Jerin Jacob
2023-04-24 22:31 ` Thomas Monjalon
2023-04-10 13:42 ` Konstantin Ananyev
2023-04-19 15:40 ` Kevin Traynor
2023-04-20 10:17 ` Jerin Jacob
2023-05-18 13:21 ` [dpdk-dev] [PATCH v1] doc: process for " jerinj
2023-06-06 16:06 ` Jerin Jacob
2023-07-20 6:33 ` Jerin Jacob [this message]
2023-07-20 8:03 ` Ferruh Yigit
2023-07-25 10:19 ` Thomas Monjalon
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='CALBAE1O-aEEQTGjHFT9zn3OSoyU4S_dgHj57WdiSh7Cp=6-zQg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.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 NNTP newsgroup(s).