From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 2443B2B92 for ; Thu, 30 Aug 2018 10:36:52 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6FA5221EAB; Thu, 30 Aug 2018 04:36:51 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 30 Aug 2018 04:36:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ZWMslUBJ/DlG3YRNNukRfamv1f AVrzRwLXSQ/UoHckA=; b=O0ry8y1R2TtRyvj5HSIkMGkhzEjJcebaJWcdpO8wFl Jj5yilhfGBxc7APFg+j68F6Z0pjhNMLGt2eKck5y85aoutYpNa/iUoeA+JxKkZzu p9RXF/DApHWDSSoBgVcYis4h16Z3k4+eTbk++kaSx8roSXTuLfynqkCEfKZlL5l3 c= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=ZWMslU BJ/DlG3YRNNukRfamv1fAVrzRwLXSQ/UoHckA=; b=J2CGhM6HoI2OSw7ZyKW9Fp 1KxzYeGQdRIQoJQarH+lYmsfI0nxvyID6gEXomgY48bVQJrNFw/rSLF9xzOpShFN RbveMx0OhWGNGDJTQ1ppJMsgiGmKRHBO/MFpucV67AZd+dmBD9XMNMDW1/hoUDQI jUPMQDZPIcNSN6rdfSy/mw1QeIoJ3/3EKu51xwxa8eW9byL/zTjpwQhn25DsN2Ad aJ9PXLVIlzQT69vXuEFstEl8YYX4Cvm9Tx5i1HgNCfkE1BNnX2h6sRG5z/A+wSIW TTqabaD402c7G5VVX3HwQ4BH9yqy/ZpPUhadfKhf3ij4fypqvy+WjIWUdkNkV0ig == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id A836410299; Thu, 30 Aug 2018 04:36:48 -0400 (EDT) From: Thomas Monjalon To: Christian Ehrhardt , Gowrishankar Muthukrishnan , Chao Zhu , pradeep@us.ibm.com, Alfredo Mendoza , Gowrishankar Muthukrishnan , Gowrishankar Muthukrishnan , Kevin Reilly Cc: dev@dpdk.org, adrien.mazarguil@6wind.com, Luca Boccassi Date: Thu, 30 Aug 2018 10:36:46 +0200 Message-ID: <3195236.p3PdHVbfnl@xps> In-Reply-To: References: <20180829131605.GJ3695@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] 18.08 build error on ppc64el - bool as vector type X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 08:36:52 -0000 29/08/2018 16:37, Christian Ehrhardt: > Why is no-one of IBM/Power world replying at all? > There not even was a "oh yeah, " mail by > them. > Is in fact ppc64 support in DPDK dead or at least "unmaintained"? > This is something that mid term has to be sorted out - I tried to pull some > strings to get attention "there" but so far I'm waiting for a reply. > I'd say 18.11 should not be released with a clear re-confirmation of ppc64 > maintainance ppc64 by "someone". I tend to agree. Let's try again: Chao, are you still available for DPDK PPC maintenance? SHOULD WE DECLARE DPDK NOT SUPPORTED ON PPC64?