DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: jerinj@marvell.com, Liron Himi <lironh@marvell.com>,
	Jerin Jacob <jerinjacobk@gmail.com>
Cc: dev@dpdk.org, Ori Kam <orika@nvidia.com>,
	Prasun Kapoor <pkapoor@marvell.com>
Subject: Re: [PATCH] regex/cn9k: remove rule compiler
Date: Mon, 03 Jul 2023 16:59:48 +0200	[thread overview]
Message-ID: <3242368.44csPzL39Z@thomas> (raw)
In-Reply-To: <CALBAE1MQaS5zaZf=D2-im34RQkVviA0NGY-sDnPQ20TZ5V6Lfg@mail.gmail.com>

21/06/2023 17:33, Jerin Jacob:
> On Wed, Jun 21, 2023 at 7:36 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > Nobody knows how to build the feature.
> > When the dependency "rxp_compiler" is found,
> > the header file is not available:
> >
> > drivers/regex/cn9k/cn9k_regexdev_compiler.c:12:10: fatal error:
> >         rxp-compiler.h: No such file or directory
> >
> > It seems that it depends on a proprietay library.
> 
> Yes. it depended on proprietary library owned by NVIDIA now. Not sure
> Marvell has rights to publish it "freely available".
> In order to avoid forking this library, better option to make this
> library as public. Also, it looks like the library itself won't have
> proper installation procedures that is the
> reason for conflict as documented here in
> https://bugs.dpdk.org/show_bug.cgi?id=1232.
> 
> If that is not an option for other original owner, I think, it should
> be removed and accept this patch in the true sprint of open source.
> 
> Acked-by: Jerin Jacob <jerinj@marvell.com>

Applied



      parent reply	other threads:[~2023-07-03 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 14:06 Thomas Monjalon
2023-06-21 15:33 ` Jerin Jacob
2023-06-25 20:57   ` Stephen Hemminger
2023-06-26  7:16     ` Thomas Monjalon
2023-06-26 16:22       ` Stephen Hemminger
2023-06-26 16:43         ` Thomas Monjalon
2023-06-26 17:11           ` Stephen Hemminger
2023-07-03 14:59   ` Thomas Monjalon [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=3242368.44csPzL39Z@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=lironh@marvell.com \
    --cc=orika@nvidia.com \
    --cc=pkapoor@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).