DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Liu, Yu Y" <yu.y.liu@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
	Jan Medala <jan@semihalf.com>,
	dev@dpdk.org, "Cao, Waterman" <waterman.cao@intel.com>,
	"Chen, WeichunX" <weichunx.chen@intel.com>,
	"Xu, HuilongX" <huilongx.xu@intel.com>,
	"Glynn, Michael J" <michael.j.glynn@intel.com>,
	"Gu, YongjieX" <yongjiex.gu@intel.com>,
	"Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] dpdk daily build error on dpdk16.07-rc2
Date: Thu, 14 Jul 2016 14:48:44 +0200	[thread overview]
Message-ID: <2029172.eKyuoxE5qy@xps13> (raw)
In-Reply-To: <D9E7459352598649B9DF0563CBC90AEB39F9ED68@SHSMSX101.ccr.corp.intel.com>

2016-07-14 11:34, Liu, Yu Y:
> Hi Thomas,
> 
> Would you check who can work on "dpdk16.07-rc2 compile error on FC18 & UB1204"?

I think I've already fixed it:
	http://dpdk.org/ml/archives/dev/2016-July/043918.html

> For "dpdk16.07-rc2 compile error on suse11", I saw document shows we support suse12+.
> Seems it is not issue for this release.
> Agree?

If there is a fix, I will apply it.
But yes you can stop testing Suse 11.

  reply	other threads:[~2016-07-14 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14  9:23 Gu, YongjieX
2016-07-14 11:34 ` Liu, Yu Y
2016-07-14 12:48   ` Thomas Monjalon [this message]
2016-07-15 11:13 ` Liu, Yu Y
2016-07-15 11:17   ` Jan Mędala
2016-07-19 10:27 ` Liu, Yu Y

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=2029172.eKyuoxE5qy@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=huilongx.xu@intel.com \
    --cc=jan@semihalf.com \
    --cc=michael.j.glynn@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=sergio.gonzalez.monroy@intel.com \
    --cc=waterman.cao@intel.com \
    --cc=weichunx.chen@intel.com \
    --cc=yongjiex.gu@intel.com \
    --cc=yu.y.liu@intel.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).