From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Stephen Hemminger <stephen@networkplumber.org>,
dev <dev@dpdk.org>, Ray Kinsella <mdr@ashroe.eu>,
Thomas Monjalon <thomas@monjalon.net>,
Olivier Matz <olivier.matz@6wind.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] mbuf: enforce no option for dynamic fields and flags
Date: Fri, 15 Oct 2021 10:28:24 +0200 [thread overview]
Message-ID: <CAJFAV8w4bcKU_95gDA7sDawx=WiH+GKhD06JTt6puW1gkCTL2Q@mail.gmail.com> (raw)
In-Reply-To: <6503ad46-fca3-f3c8-6023-2eab27f8e7b8@oktetlabs.ru>
On Wed, Oct 13, 2021 at 9:06 AM Andrew Rybchenko
<andrew.rybchenko@oktetlabs.ru> wrote:
> On 10/12/21 11:14 PM, Stephen Hemminger wrote:
> > On Tue, 12 Oct 2021 21:39:57 +0200
> > David Marchand <david.marchand@redhat.com> wrote:
> >
> >> As stated in the API, dynamic field and flags should be created with no
> >> additional flag (simply in the API for future changes).
> >>
> >> Fix the dynamic flag register helper which was not enforcing it and add
> >> unit tests.
> >>
> >> Fixes: 4958ca3a443a ("mbuf: support dynamic fields and flags")
> >>
> >> Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Acked-by: Ray Kinsella <mdr@ashroe.eu>
Applied, thanks.
--
David Marchand
next prev parent reply other threads:[~2021-10-15 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 19:39 David Marchand
2021-10-12 20:14 ` Stephen Hemminger
2021-10-13 7:06 ` Andrew Rybchenko
2021-10-15 8:28 ` David Marchand [this message]
2021-10-13 8:37 ` Kinsella, Ray
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='CAJFAV8w4bcKU_95gDA7sDawx=WiH+GKhD06JTt6puW1gkCTL2Q@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=mdr@ashroe.eu \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.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).