From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id A9E70A00E6 for ; Thu, 16 May 2019 11:41:58 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9005C5F14; Thu, 16 May 2019 11:41:57 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id AB8D75A6A for ; Thu, 16 May 2019 11:41:55 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 304E02372; Thu, 16 May 2019 05:41:55 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 16 May 2019 05:41:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=BIUQL1YaTzDPjjYYgIBnAX4jC7ANOO5VI9o2+9dn0SU=; b=MQyJmicn8kCI jfW12neJiSPFlxuDTUHVblTTaCjzEzC/kGCzOcY3qXf5cmeXPcPOgQLQUBnvv8hc Dxf2oaGkNInjaEd4kHR6vninmGO5O2KQ5jAbdlr1VCIMq+2PW+uA9vuVTPxf7Jc6 x7jZpvRcfBf58gmP4HHmhI2vjVGNy5c= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=BIUQL1YaTzDPjjYYgIBnAX4jC7ANOO5VI9o2+9dn0 SU=; b=yA++wyPrIjv80gCbs585qLa8FeJf4FzEmsI6HGDc20P8dWLjM4YdZQBOf CXo2YWB/OVvtFeJQHDqKWFIryMVuYe1EeZL9tKzHX5Gj2SuwUWg/67icuEXWCLzC ueKyJxJ+a1a4X7JqIycRfvPbsdQ5N1BS6Q52Zv0/4O/M/kfPcjjuzsR/Ir3hCMm+ leD+JhNBluj15yGEuUuny2TzHDoJyWDuDfUApRkdIlm2h1bk2fGPSdvzhJDxC4Bd VO/laWiYq5DzYCdsJPkqx6L/hYxLaHBDwhVDFQ7pNSWL2HtWiEgq6A+hmMhKq3Kf zUDgROcVzEk5N1Iv3mRDavXMLZWzA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddruddttddgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 8432480065; Thu, 16 May 2019 05:41:52 -0400 (EDT) From: Thomas Monjalon To: Ranjit Menon , cathal.ohare@intel.com, harini.ramakrishnan@microsoft.com Cc: dev@dpdk.org, pallavi.kadam@intel.com, bruce.richardson@intel.com, rasland@mellanox.com, Adham Masarwah , Eilon Greenstein , Anan Saif , Rani Sharoni , Tal Alon , Yohad Tor , Omar Cardona , Haseeb.Gani@cavium.com, shshaikh@marvell.com, nareshkumar.pbs@broadcom.com Date: Thu, 16 May 2019 11:41:50 +0200 Message-ID: <3423275.GdfnmaGHQd@xps> In-Reply-To: <2605026.pMiyh1GXVC@xps> References: <1a8d7d89-bc0b-33d4-f4bc-e8284cbd2958@intel.com> <2605026.pMiyh1GXVC@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] DPDK Windows Community call - 02 May 2019 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190516094150.CcjoUeljRIAUjk-jNJFFxivCHlQflCcjbc1OfVmqe74@z> 14/05/2019 17:48, Thomas Monjalon: > 10/05/2019 01:34, Ranjit Menon: > > Contact Cathal to be added to this meeting invite. > > Would it be possible to move this bi-weekly meeting > to the Tuesday (same time), please? > > [...] > > Encourage other dpdk.org Windows partners to join this call. > > Yes, would be nice to hear more developers joining the party. > [...] > What is the status of the PCI code in drivers/bus/pci? > Is someone working on it with clang and meson? > Mellanox would like to join the effort on PCI. Please add the Mellanox engineers who are Cc of this mail. Mellanox is ramping up. We need to know how to proceed with the PCI code.