From: Akhil Goyal <gakhil@marvell.com>
To: "Akhil Goyal" <gakhil@marvell.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Fan Zhang" <fanzhang.oss@gmail.com>
Cc: "hofors@lysator.liu.se" <hofors@lysator.liu.se>,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: RE: [EXTERNAL] [PATCH] cryptodev: allow use of global variables from C++
Date: Sun, 2 Mar 2025 18:37:43 +0000 [thread overview]
Message-ID: <CO6PR18MB44844D176B4FF094210B4C53D8CE2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB448445B1358C95D3556FAD2BD8122@CO6PR18MB4484.namprd18.prod.outlook.com>
Hi Mattias,
Can you update this patch?
> > Avoid C++ name mangling of the two global variables being exported
> > from <rte_crypto_asym.h>.
> >
> > Suggested-by: David Marchand <david.marchand@redhat.com>
> > Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
> > ---
> > lib/cryptodev/rte_crypto_asym.h | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/lib/cryptodev/rte_crypto_asym.h
> b/lib/cryptodev/rte_crypto_asym.h
> > index aeb46e688e..9787b710e7 100644
> > --- a/lib/cryptodev/rte_crypto_asym.h
> > +++ b/lib/cryptodev/rte_crypto_asym.h
> > @@ -25,6 +25,10 @@
> >
> > struct rte_cryptodev_asym_session;
> >
> > +#ifdef __cplusplus
> > +extern "C" {
> > +#endif
> > +
> > /** asym key exchange operation type name strings */
> > extern const char *
> > rte_crypto_asym_ke_strings[];
> > @@ -33,6 +37,10 @@ rte_crypto_asym_ke_strings[];
> > extern const char *
> > rte_crypto_asym_op_strings[];
> >
> > +#ifdef __cplusplus
> > +}
> > +#endif
> > +
> > #define RTE_CRYPTO_ASYM_FLAG_PUB_KEY_NO_PADDING
> > RTE_BIT32(0)
>
> It seems only these two variables are causing problem,
> but shouldn't it be better to have this change for the complete file
> like rte_crypto_sym.h.
> This will avoid issues with any future additions.
prev parent reply other threads:[~2025-03-02 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 16:35 Mattias Rönnblom
2025-01-08 9:55 ` [EXTERNAL] " Akhil Goyal
2025-03-02 18:37 ` 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=CO6PR18MB44844D176B4FF094210B4C53D8CE2@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=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).