From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Shijith Thotton <sthotton@marvell.com>,
Radha Mohan Chintakuntla <radhac@marvell.com>,
Veerasenareddy Burru <vburru@marvell.com>,
Sathesh Edara <sedara@marvell.com>,
jerinj@marvell.com
Subject: Re: [PATCH v3 2/4] crypto/cnxk: restructure for cn10k datapath
Date: Tue, 7 Feb 2023 17:43:46 +0530 [thread overview]
Message-ID: <CALBAE1MD4qGZVbShNPGAvFZ+tzG6nfMV_BOHnBvrswJsz2mRCQ@mail.gmail.com> (raw)
In-Reply-To: <20230125113126.2860273-2-rbhansali@marvell.com>
On Wed, Jan 25, 2023 at 5:02 PM Rahul Bhansali <rbhansali@marvell.com> wrote:
>
> From: Anoob Joseph <anoobj@marvell.com>
>
> Inclusion of roc_api.h in all files would mean any change in RoC API
> would result in recompilation of all cnxk drivers. Address this issue in
> crypto_cnxk drivers by including only the headers that are required.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> ---
> Changes in v3: Reorder patch in series for compilation fix.
> Changes in v2: Updated git comment subject.
> /* SSO Operations */
> diff --git a/drivers/net/octeon_ep/meson.build b/drivers/net/octeon_ep/meson.build
> index a267b60290..a3bfed09ee 100644
> --- a/drivers/net/octeon_ep/meson.build
> +++ b/drivers/net/octeon_ep/meson.build
> @@ -2,6 +2,8 @@
> # Copyright(C) 2021 Marvell.
> #
>
> +deps += ['common_cnxk']
This changes is not needed as octeon_ep driver is not using roc_ APIs.
Have updated the patch with above change
Series applied to dpdk-next-net-mrvl/for-next-net. Thanks
> +
> sources = files(
> 'otx_ep_ethdev.c',
> 'otx_ep_rxtx.c',
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-02-07 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 9:15 [PATCH 1/4] common/cnxk: " Rahul Bhansali
2022-12-21 9:15 ` [PATCH 2/4] net/cnxk: " Rahul Bhansali
2023-01-17 8:52 ` Jerin Jacob
2023-01-17 10:24 ` [EXT] " Rahul Bhansali
2022-12-21 9:15 ` [PATCH 3/4] crypto/cnxk: include only files that are used Rahul Bhansali
2022-12-21 9:15 ` [PATCH 4/4] event/cnxk: restructure for cn10k datapath Rahul Bhansali
2023-01-18 10:26 ` [PATCH v2 1/4] common/cnxk: " Rahul Bhansali
2023-01-18 10:27 ` [PATCH v2 2/4] net/cnxk: " Rahul Bhansali
2023-01-25 4:58 ` Jerin Jacob
2023-01-25 6:22 ` [EXT] " Rahul Bhansali
2023-01-18 10:27 ` [PATCH v2 3/4] crypto/cnxk: " Rahul Bhansali
2023-01-18 10:27 ` [PATCH v2 4/4] event/cnxk: " Rahul Bhansali
2023-01-25 11:31 ` [PATCH v3 1/4] common/cnxk: " Rahul Bhansali
2023-01-25 11:31 ` [PATCH v3 2/4] crypto/cnxk: " Rahul Bhansali
2023-02-07 12:13 ` Jerin Jacob [this message]
2023-01-25 11:31 ` [PATCH v3 3/4] net/cnxk: " Rahul Bhansali
2023-01-25 11:31 ` [PATCH v3 4/4] event/cnxk: " Rahul Bhansali
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=CALBAE1MD4qGZVbShNPGAvFZ+tzG6nfMV_BOHnBvrswJsz2mRCQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ktejasree@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=radhac@marvell.com \
--cc=rbhansali@marvell.com \
--cc=sedara@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=sthotton@marvell.com \
--cc=vburru@marvell.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).