From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com
 [209.85.215.42]) by dpdk.org (Postfix) with ESMTP id 431763237
 for <dev@dpdk.org>; Thu, 14 Jul 2016 14:48:47 +0200 (CEST)
Received: by mail-lf0-f42.google.com with SMTP id b199so62875049lfe.0
 for <dev@dpdk.org>; Thu, 14 Jul 2016 05:48:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=6wind-com.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:subject:date:message-id:user-agent:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=pMlNoX3Hh0nHqtTe8qzXZ798lbhxGikpEpLjLd7jX2E=;
 b=fivGOmiR2U2R7pEenhakl4fuhbsXBhV1awATFaKlIzC49kJK+LeYCxguB9x9KFrEip
 JxY+Gh/U5ZoGp6VmUY5lxt2eGn1B4pZj+qrgarj9eOxcsuI7aTM5aVYv9u3I37hKfSlQ
 ACGj2UGd7N8DdZwGPL0GCCaqPpG8l1gPwt6++be1D8vwd8/kiYxVSj6MSfXp6vZIaNJq
 51sHLn2057pQqRbjGYnSX3BInoZW3TrFNdXmGP7zOXZOegEZXrICcAolv0X8qtBV4r4Z
 WmEE4AchWTyzhMZcFpa6MgqEPUpg1RA/ViYKu5g2nIxEI8TGJoZGcdDhaxY9ObTaVvoy
 tN6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent
 :in-reply-to:references:mime-version:content-transfer-encoding;
 bh=pMlNoX3Hh0nHqtTe8qzXZ798lbhxGikpEpLjLd7jX2E=;
 b=GLV2CF/SLp2QTYo/7NdGhq/htlKJGLNGZb1PDMvtolYiQSCq9vLjj12lxvt2OmUU7j
 Y4xLEThE9nVyFVzj77Rmaerqs4w3TdKMgmjv7tdqam7UyeTAT42yhKnDn4UHXrjo968B
 nLF/vgyC7Fhh3Kn/6rrKEHW5B9U7qPc+CvG2jbvVjwTFO5dCmcKvxZsgFvbYQxGK326r
 sQH12q0PG2Pi3+5T/RQpmEsbK20Tkuo4JC4HhUD3xg51E7Rbb36fIYLV3EhpqYDDV7Jv
 r9q/B0Qa47W8Pht1tMMGzcVVC5QRMEzdTs5NAZrSFWFq/swsZHmK5teIFIXN+WtUyb+F
 2KTg==
X-Gm-Message-State: ALyK8tIyeJexu56/qEAjnnV7iV971nZkq8cH2hNutusutbAvdMPqB1d+SaanGdl9d/t5Zdw6
X-Received: by 10.25.20.69 with SMTP id k66mr6163194lfi.35.1468500526858;
 Thu, 14 Jul 2016 05:48:46 -0700 (PDT)
Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184])
 by smtp.gmail.com with ESMTPSA id u2sm325675lja.16.2016.07.14.05.48.45
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 14 Jul 2016 05:48:46 -0700 (PDT)
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>
Date: Thu, 14 Jul 2016 14:48:44 +0200
Message-ID: <2029172.eKyuoxE5qy@xps13>
User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; )
In-Reply-To: <D9E7459352598649B9DF0563CBC90AEB39F9ED68@SHSMSX101.ccr.corp.intel.com>
References: <E1E7EC9273ACA248A8E9BE46A66CE0A03EBCE21C@SHSMSX101.ccr.corp.intel.com>
 <D9E7459352598649B9DF0563CBC90AEB39F9ED68@SHSMSX101.ccr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] dpdk daily build error on dpdk16.07-rc2
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2016 12:48:47 -0000

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.