From: Thomas Monjalon <thomas@monjalon.net>
To: Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com, maxime.coquelin@redhat.com,
trix@redhat.com, ray.kinsella@intel.com,
bruce.richardson@intel.com, hemant.agrawal@nxp.com,
david.marchand@redhat.com, stephen@networkplumber.org
Subject: Re: [PATCH v4] doc: announce changes in bbdev related to enum extension
Date: Sun, 17 Jul 2022 11:48:45 +0200 [thread overview]
Message-ID: <2377045.jE0xQCEvom@thomas> (raw)
In-Reply-To: <1654734870-131398-2-git-send-email-nicolas.chautru@intel.com>
09/06/2022 02:34, Nicolas Chautru:
> Intent to resolve in DPDK 22.11 historical usage which prevents
> graceful extension of enum and API without troublesome ABI breakage
> as well as extending API RTE_BBDEV_OP_FFT for new operation type
> in bbdev as well as other new members in existing structures.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Improved links and applied, thanks.
prev parent reply other threads:[~2022-07-17 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 18:37 [PATCH v2] doc: announce changes in bbdev related to enum extension Nicolas Chautru
2022-03-17 18:37 ` Nicolas Chautru
2022-06-09 0:20 ` [PATCH v3] " Nicolas Chautru
2022-06-09 0:20 ` Nicolas Chautru
2022-06-09 0:34 ` [PATCH v4] " Nicolas Chautru
2022-06-09 0:34 ` Nicolas Chautru
2022-06-09 5:14 ` Hemant Agrawal
2022-06-09 7:53 ` Maxime Coquelin
2022-06-17 16:13 ` Chautru, Nicolas
2022-06-27 20:47 ` Chautru, Nicolas
2022-06-30 14:52 ` Chautru, Nicolas
2022-07-05 15:45 ` Bruce Richardson
2022-07-17 9:48 ` 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=2377045.jE0xQCEvom@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.com \
--cc=ray.kinsella@intel.com \
--cc=stephen@networkplumber.org \
--cc=trix@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.