From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Anoob Joseph <anoobj@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/octeontx2: enable driver compilation on freebsd
Date: Thu, 25 Feb 2021 18:06:24 +0530 [thread overview]
Message-ID: <CALBAE1P0hdgiveZaZewB3DNm+KU_6ytEJ7XszyuOh=xm9ROpPQ@mail.gmail.com> (raw)
In-Reply-To: <20210225122802.7029-1-pbhagavatula@marvell.com>
On Thu, Feb 25, 2021 at 5:58 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Enable compilation on freebsd.
Since DPDK octeontx2 drivers have a dependency on Linux kernel driver,
I think, in order to simply this stuff, we can completely remove the
FreeBSD support in octeontx and octeontx2 drivers.
Since we are supporting x86-64 bit compilation support, that would
enable others contribute without have an octeontx2 machine.
We may not need FreeBSD support to establish this support.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> drivers/crypto/octeontx2/meson.build | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/octeontx2/meson.build b/drivers/crypto/octeontx2/meson.build
> index 283818e5d..063f53253 100644
> --- a/drivers/crypto/octeontx2/meson.build
> +++ b/drivers/crypto/octeontx2/meson.build
> @@ -1,9 +1,9 @@
> # SPDX-License-Identifier: BSD-3-Clause
> # Copyright (C) 2019 Marvell International Ltd.
>
> -if not is_linux or not dpdk_conf.get('RTE_ARCH_64')
> +if not dpdk_conf.get('RTE_ARCH_64')
> build = false
> - reason = 'only supported on 64-bit Linux'
> + reason = 'only supported on 64-bit arch'
> subdir_done()
> endif
>
> --
> 2.17.1
>
prev parent reply other threads:[~2021-02-25 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 12:28 pbhagavatula
2021-02-25 12:36 ` Jerin Jacob [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='CALBAE1P0hdgiveZaZewB3DNm+KU_6ytEJ7XszyuOh=xm9ROpPQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@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).