From: Akhil Goyal <gakhil@marvell.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>,
"Thomas Monjalon" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Zhigang Hu" <zhigang.hu@intel.com>,
"Fan Zhang" <fanzhang.oss@gmail.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"David Marchand" <david.marchand@redhat.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: RE: [EXTERNAL] Re: [PATCH v2] cryptodev: fix C++ include
Date: Wed, 8 Jan 2025 10:35:27 +0000 [thread overview]
Message-ID: <CO6PR18MB4484A9C5F8609CFE3FE0E33ED8122@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <fa4d764a-b632-4551-b577-1682769aed67@lysator.liu.se>
> On 2024-12-19 14:30, Thomas Monjalon wrote:
> > Some cryptodev functions were not included in an extern "C" block.
> >
> > There are 2 blocks, the second one being fast path inline functions,
> > preceded with an include of the required rte_cryptodev_core.h file.
> >
> > Fixes: 719834a6849e ("use C linkage where appropriate in headers")
> > Cc: stable@dpdk.org
> >
> > Reported-by: Zhigang Hu <zhigang.hu@intel.com>
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> > v2: keep rte_cryptodev_core.h include at the same place
> Reviewed-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2025-01-08 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 10:41 The question for the modification against (lib/cryptodev/rte_cryptodev.h) in commit 719834a6 Hu, Zhigang
2024-12-19 11:45 ` [PATCH] cryptodev: fix C++ include Thomas Monjalon
2024-12-19 12:24 ` [EXTERNAL] " Akhil Goyal
2024-12-19 12:36 ` Thomas Monjalon
2024-12-19 11:48 ` The question for the modification against (lib/cryptodev/rte_cryptodev.h) in commit 719834a6 Thomas Monjalon
2024-12-20 2:17 ` Hu, Zhigang
2024-12-20 2:21 ` Hu, Zhigang
2024-12-19 13:30 ` [PATCH v2] cryptodev: fix C++ include Thomas Monjalon
2024-12-19 15:37 ` David Marchand
2024-12-19 16:36 ` Mattias Rönnblom
2024-12-19 16:34 ` Mattias Rönnblom
2025-01-08 10:35 ` Akhil Goyal [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=CO6PR18MB4484A9C5F8609CFE3FE0E33ED8122@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=hofors@lysator.liu.se \
--cc=mattias.ronnblom@ericsson.com \
--cc=mb@smartsharesystems.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=zhigang.hu@intel.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 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).