DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [pull-request] next-pipeline 18.05 PRE-RC1
Date: Wed, 04 Apr 2018 09:53:30 +0200	[thread overview]
Message-ID: <4804393.3nlcFQs5t0@xps> (raw)
In-Reply-To: <1522413935-118517-1-git-send-email-cristian.dumitrescu@intel.com>

Hi,

30/03/2018 14:45, Cristian Dumitrescu:
>   http://dpdk.org/git/next/dpdk-next-pipeline 

I saw 2 issues:
	- table_index is wrongly placed in doxygen index
	- compilation error with clang: status_data is used uninitialized

  reply	other threads:[~2018-04-04  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30 12:45 Cristian Dumitrescu
2018-04-04  7:53 ` Thomas Monjalon [this message]
2018-04-04 10:47   ` Dumitrescu, Cristian
2018-04-05  0:03     ` Thomas Monjalon
2018-04-05 11:00       ` Dumitrescu, Cristian
2018-04-06 16:45         ` Thomas Monjalon

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=4804393.3nlcFQs5t0@xps \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    /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).