DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Vidya Sagar Velumuri <vvelumuri@marvell.com>, dev <dev@dpdk.org>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [EXT] Re: [Bug 828] [dpdk-21.11] zuc unit test is failing
Date: Mon, 18 Oct 2021 21:42:39 +0000	[thread overview]
Message-ID: <CO6PR18MB448419547DC298BC8BB86F8AD8BC9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xd=3_QycJbrCGsSsQGxGn4Xg=2wicOVDn=gc0HyBa9JQ@mail.gmail.com>

> > Can somebody from Intel look into this?
> > We don’t have intel-ipsec-mb library access, so cannot reproduce the issue.
> 
> I see Intel reply on the issue so we are probably good.
> 
> However, on access to intel-ipsec-mb topic, sources are available on github.
> Compiling is relatively easy (this is what I did in the past when
> checking compilation) if your linux distributions does not package it,
> but some do:
Sorry, I meant we don’t have setup to test with intel-ipsec-mb.
The issue is not about compilation. It is about a failing test case while running it.

      reply	other threads:[~2021-10-18 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  8:02 [dpdk-dev] " bugzilla
2021-10-15  8:14 ` David Marchand
2021-10-15 18:04   ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-16  5:04     ` Vidya Sagar Velumuri
2021-10-16 13:10     ` Zhang, Roy Fan
2021-10-18  7:46     ` David Marchand
2021-10-18 21:42       ` 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=CO6PR18MB448419547DC298BC8BB86F8AD8BC9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=vvelumuri@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).