DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, John McNamara <john.mcnamara@intel.com>,
	 "Stokes, Ian" <ian.stokes@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"Akhil, Goyal" <akhil.goyal@nxp.com>,
	 Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Qian Xu <qian.q.xu@intel.com>,  Yongseok Koh <yskoh@mellanox.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	 Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 11/4/2019
Date: Fri, 12 Apr 2019 03:48:36 +0300	[thread overview]
Message-ID: <CAHLOa7S_DO2DwG9ow3jxjg-N2zOHnp_H67Q5Egpc4zrLjvaSfQ@mail.gmail.com> (raw)
Message-ID: <20190412004836.MSn1lgaVDORc8bPYxBqjF3Lb9pHc-46ycEG8UaG3oCU@z> (raw)
In-Reply-To: <16b375ee-bc7a-1d2e-1815-e2ae12f5f21a@intel.com>

Hi,
>* Coverity is up and there are already some fixes hit the mail list,
  >this is good progress, as a reminder, coverity dpdk project link:
  >
https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview
>  (As of now link is not working for me but hopefully it will come back)

Link was not work also for me, but now is started working all if a
sudden...:)

Regards,
Rami Rosen

  parent reply	other threads:[~2019-04-12  0:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 15:43 Ferruh Yigit
2019-04-11 15:43 ` Ferruh Yigit
2019-04-12  0:48 ` Rami Rosen [this message]
2019-04-12  0:48   ` Rami Rosen

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=CAHLOa7S_DO2DwG9ow3jxjg-N2zOHnp_H67Q5Egpc4zrLjvaSfQ@mail.gmail.com \
    --to=ramirose@gmail.com \
    --cc=akhil.goyal@nxp.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ian.stokes@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=yskoh@mellanox.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).