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 A2F9FA00E6 for ; Thu, 16 May 2019 15:10:29 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A35505F21; Thu, 16 May 2019 15:10:28 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id B457B5F20 for ; Thu, 16 May 2019 15:10:27 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 3C890104BB; Thu, 16 May 2019 09:10:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 16 May 2019 09:10:27 -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=9aSg3LAJEmdUBeBhR45QPfcIFdAlM0XlL6Qaru//GCY=; b=KCltUhPjdysW SU6KMlCC+9axAaobmUhwsC+8Nc7tBNt85qTiCiI4DVoscrMoNpsXX4RxkzfdFJa+ 341gvxZlFPBLeP00tQ75EGP6QHPru2aEdWi3q9qPyJvXEvBRtO/3cOv0ULdv+IAr ncaAEgPx+xo0lirLl8DnnMCvzFJv47k= 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=9aSg3LAJEmdUBeBhR45QPfcIFdAlM0XlL6Qaru//G CY=; b=N5v0BOJH9CO6BHPklgy5XvyVCriN1CVOI7LiYgEDWUsRcSpJZY5xQgBbL Ou4rB/+iITxc4JU1c7hAeHB+TTAE0noFKf4qxdr+m4ELGSzjlLtgX04ejCcCJ3ax PbbdbE00UPlqVbr6JjGuANJEqJCxZ9jAXXN/dHk/OVDrqds9PFs8Z7wSUECbOONV ykGVOQ38p6rBQKcpCb+1ESgYYtOQ6qrrTvZS5XoK3UQqI+ZInG+RWGifEi0CIEmz fikGs6hCojASU68RNVJ6vrmOReGREoYtL22RHuLKh+rS5r5otWhE3JYHatNA/CRJ yK3M+IofLN3ATZLpXQ+0BGAtogPvw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddruddttddgiedtucetufdoteggodetrfdotf 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 1A64B8005A; Thu, 16 May 2019 09:10:24 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: Ranjit Menon , cathal.ohare@intel.com, harini.ramakrishnan@microsoft.com, pallavi.kadam@intel.com, bruce.richardson@intel.com, rasland@mellanox.com, Adham Masarwah , Eilon Greenstein , Anan Saif , Rani Sharoni , Yohad Tor , Omar Cardona , Haseeb.Gani@cavium.com, shshaikh@marvell.com, nareshkumar.pbs@broadcom.com, Tal Shnaiderman Date: Thu, 16 May 2019 15:10:21 +0200 Message-ID: <1935548.CojDo964dP@xps> In-Reply-To: <3423275.GdfnmaGHQd@xps> References: <1a8d7d89-bc0b-33d4-f4bc-e8284cbd2958@intel.com> <2605026.pMiyh1GXVC@xps> <3423275.GdfnmaGHQd@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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" sending again with fixed Cc list 16/05/2019 11:41, Thomas Monjalon: > 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.