From: Thomas Monjalon <thomas@monjalon.net>
To: Olivier Matz <olivier.matz@6wind.com>,
Jerin Jacob <jerinjacobk@gmail.com>
Cc: dev@dpdk.org, techboard@dpdk.org,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] mbuf: document guideline for new fields and flags
Date: Thu, 11 Jun 2020 09:30:10 +0200 [thread overview]
Message-ID: <318373323.FDTIfyX7Cs@thomas> (raw)
In-Reply-To: <CALBAE1OfK12HaMLtwS-An+DPKuxvRkhe0mn6n2oLSaUGbcFuLw@mail.gmail.com>
11/06/2020 08:37, Jerin Jacob:
> On Thu, Jun 11, 2020 at 12:02 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > Since dynamic fields and flags were added in 19.11,
> > the idea was to use them for new features, not only PMD-specific.
> >
> > The guideline is made more explicit in doxygen, in the mbuf guide,
> > and in the contribution design guidelines.
> >
> > For more information about the original design, see the presentation
> > https://www.dpdk.org/wp-content/uploads/sites/35/2019/10/DynamicMbuf.pdf
> >
> > This decision was discussed in the Technical Board:
> > http://mails.dpdk.org/archives/dev/2020-June/169667.html
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > Acked-by: Olivier Matz <olivier.matz@6wind.com>
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied
prev parent reply other threads:[~2020-06-11 7:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 21:24 [dpdk-dev] [PATCH] mbuf: document rule " Thomas Monjalon
2020-05-26 7:39 ` Jerin Jacob
2020-05-26 16:06 ` Olivier Matz
2020-05-26 16:29 ` Jerin Jacob
2020-05-27 7:09 ` Olivier Matz
2020-05-27 7:31 ` Jerin Jacob
2020-05-27 9:51 ` Thomas Monjalon
2020-05-27 11:43 ` Jerin Jacob
2020-05-27 11:56 ` Thomas Monjalon
2020-05-27 12:07 ` Jerin Jacob
2020-05-27 12:23 ` Olivier Matz
2020-05-27 12:34 ` Jerin Jacob
2020-06-11 6:32 ` [dpdk-dev] [PATCH v2] mbuf: document guideline " Thomas Monjalon
2020-06-11 6:37 ` Jerin Jacob
2020-06-11 7:30 ` Thomas Monjalon [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=318373323.FDTIfyX7Cs@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=olivier.matz@6wind.com \
--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).