From: Akhil Goyal <gakhil@marvell.com>
To: Shijith Thotton <sthotton@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Cc: "abhinandan.gujjar@intel.com" <abhinandan.gujjar@intel.com>,
"aconole@redhat.com" <aconole@redhat.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"lylavoie@iol.unh.edu" <lylavoie@iol.unh.edu>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Shijith Thotton <sthotton@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/octeontx: enable build on non Linux OS
Date: Thu, 22 Jul 2021 09:17:21 +0000 [thread overview]
Message-ID: <CO6PR18MB4484AED5BD861E05C8B1CC3BD8E49@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210722090651.2598075-1-sthotton@marvell.com>
> Enabled build of Octeontx crypto PMD on non linux OS. Other Octeontx
> PMDs are enabled already.
>
> This is to avoid ABI test failure on an OS once we add dependency
> between a driver which is built to another which is not.
Fixes: 8dc6c2f12ecf ("crypto/octeontx: add crypto adapter framework")
>
Reported-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Shijith Thotton <sthotton@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
Thomas/David: please pick this patch directly on main to fix build on CI for FreeBSD.
next prev parent reply other threads:[~2021-07-22 9:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 16:48 [dpdk-dev] [PATCH 0/2] OCTEONTX crypto adapter support Shijith Thotton
2021-06-22 16:48 ` [dpdk-dev] [PATCH 1/2] drivers: add octeontx crypto adapter framework Shijith Thotton
2021-06-22 16:48 ` [dpdk-dev] [PATCH 2/2] drivers: add octeontx crypto adapter data path Shijith Thotton
2021-07-06 20:20 ` Akhil Goyal
2021-06-23 20:53 ` [dpdk-dev] [PATCH v2 0/2] OCTEONTX crypto adapter support Shijith Thotton
2021-06-23 20:53 ` [dpdk-dev] [PATCH v2 1/2] drivers: add octeontx crypto adapter framework Shijith Thotton
2021-07-06 20:14 ` Akhil Goyal
2021-07-15 14:21 ` David Marchand
2021-07-16 8:39 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-20 11:58 ` Akhil Goyal
2021-07-20 12:14 ` David Marchand
2021-07-21 9:44 ` Thomas Monjalon
2021-07-21 15:11 ` Brandon Lo
2021-07-22 7:45 ` Akhil Goyal
2021-07-22 9:06 ` [dpdk-dev] [PATCH] crypto/octeontx: enable build on non Linux OS Shijith Thotton
2021-07-22 9:17 ` Akhil Goyal [this message]
2021-07-22 19:06 ` Thomas Monjalon
2021-07-22 19:08 ` Thomas Monjalon
2021-07-22 20:20 ` Brandon Lo
2021-07-22 20:32 ` Thomas Monjalon
2021-06-23 20:53 ` [dpdk-dev] [PATCH v2 2/2] drivers: add octeontx crypto adapter data path Shijith Thotton
2021-06-30 8:54 ` Akhil Goyal
2021-06-30 16:23 ` [dpdk-dev] [dpdk-ci] " Brandon Lo
2021-07-07 9:28 ` [dpdk-dev] [PATCH v2 0/2] OCTEONTX crypto adapter support Akhil Goyal
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=CO6PR18MB4484AED5BD861E05C8B1CC3BD8E49@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=aconole@redhat.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=jerinj@marvell.com \
--cc=lylavoie@iol.unh.edu \
--cc=mdr@ashroe.eu \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@marvell.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).