DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>,
	 "Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] [Bug 285] rte_table unit test crashes in ipv6
Date: Fri, 28 Jun 2019 14:37:18 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E8B41DE@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8wbXtwRd8jqJarAVbp4j3zxRWHpwc2s4mTVX3Osa2Q_=Q@mail.gmail.com>

Hi David,

Jasvinder and Reshma mentioned this is looked at by someone in our team. Reshma, can you please add the relevant person to this email and have them take ownership of this issue in Bugzilla.

Thanks,
Cristian

From: David Marchand [mailto:david.marchand@redhat.com]
Sent: Friday, June 28, 2019 3:30 PM
To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
Cc: dev <dev@dpdk.org>; Thomas Monjalon <thomas@monjalon.net>; Yigit, Ferruh <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [Bug 285] rte_table unit test crashes in ipv6

On Tue, Jun 18, 2019 at 12:45 PM David Marchand <david.marchand@redhat.com<mailto:david.marchand@redhat.com>> wrote:
Hello Christian,

Could you have a look at this?
Is there someone working on it?
We will have to disable the table unit tests in CI otherwise.


Ping ?


--
David Marchand



  reply	other threads:[~2019-06-28 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 16:50 bugzilla
2019-06-18 10:45 ` David Marchand
2019-06-28 14:29   ` David Marchand
2019-06-28 14:37     ` Dumitrescu, Cristian [this message]
2019-06-28 14:42       ` Pattan, Reshma
2019-06-28 14:45         ` David Marchand

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=3EB4FA525960D640B5BDFFD6A3D891268E8B41DE@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jasvinder.singh@intel.com \
    --cc=reshma.pattan@intel.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).