From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C0736A0540 for ; Thu, 7 Jul 2022 08:51:20 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 98BE3406B4; Thu, 7 Jul 2022 08:51:20 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id D6060406B4 for ; Thu, 7 Jul 2022 08:51:19 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 70B775C00C5; Thu, 7 Jul 2022 02:51:17 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 07 Jul 2022 02:51:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1657176677; x= 1657263077; bh=WyAtBVgT0k3ZNXNbnaXDf0+CsqH+YMdyeZLzJwz4+u8=; b=g hKhynm4t9ldXELd2lykSCrZPv1Cf29MwwP5XXb51lBnT3nWZZLUacVlBHlyoBUgI 2LH+zVKgbltT9/rdBRJYL5jK1vTWUF4AEeN0gNNDyV0ig6cNew3UKPORz/Sua4wj bvcQLoNJ+vsyGYE1UgNREXay750AbMPXf2j/qWnkGocdlxK1WMKnE0cmBqAdsV5h 93/BthgqttxNrRN/TJ8rG//kQHzKLkT5yU5yfabt0FAxQc+NZdEZujRdFn0pw0Ab uTvsqQKB/Z2W9QlMfuprs+WJWL168jmbtF2qrHXHLkHnR4bL8zzg/fkr6BudtTTB 2Ia+Aa6B/qt6hY9Lz/WnQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1657176677; x= 1657263077; bh=WyAtBVgT0k3ZNXNbnaXDf0+CsqH+YMdyeZLzJwz4+u8=; b=k cwFWCcqujmmY5Nj0CjoAJyszcxDgYPGej/Ipvaw1KfvJVWNFs15SuTtrhbavukgO tIqOva53TRIhqYGpLkrkiLfJu1Gh+xv239DrZOx0AwyaTW+hW1I0dRSd6hH6EsGr rwhH8eiyFESLB8eHgl9px8Ufjt8MyKK8oLB7/3VF9WDwG1CgdDAk5wg+6X8KzdZe 1VCL3tRW1yVKar7C63pIgIS5V+0pr4jNLP3O577ohz1ZwcnYOltnl6xdhxcD1tkf u0OsqyDGv8e29n1b2guQC5fcwypJ3mrpT/cYbym14nsih2NOGdl8gom3OIiHRon/ ojKvJ5DE0/TRVsc8oiOgw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeigedguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddt ieekgfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 7 Jul 2022 02:51:16 -0400 (EDT) From: Thomas Monjalon To: "Xueming(Steven) Li" , Luca Boccassi Cc: Kevin Traynor , "christian.ehrhardt@canonical.com" , "stable@dpdk.org" Subject: Re: [19.11][20.11][21.11] ppc64 fixes backport Date: Thu, 07 Jul 2022 08:51:13 +0200 Message-ID: <6239212.097qLLJo0e@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org 06/07/2022 20:53, Luca Boccassi: > On Wed, 29 Jun 2022 at 14:40, Xueming(Steven) Li wrote: > > > > Hi LTS maintainers, > > > > Confirmed with Thomas, mlx5 PMD needs the following patches to compile with the upstream rdma-core lib. > > > > 2022-05-25 2022-06-01 b251bb7630 eal/ppc: undefine AltiVec keyword vector @Thomas Monjalon > > 2022-05-03 2022-05-25 64fcadeac0 avoid AltiVec keyword vector @Thomas Monjalon > > > > I tried to backport to 20.11.6 LTS, cherry-pick works without conflicts. > > > > Best Regards, > > Xueming Li > > Hi, > > This patch: > > 2022-05-25 2022-06-01 b251bb7630 eal/ppc: undefine AltiVec keyword > vector @Thomas Monjalon > > Looks like an incompatible change? Commit message says so too: > > "This is a compatibility breakage for applications which were using > the keyword "vector" for its AltiVec meaning." > > The first one looks like but I don't think we should pick up the > second one for the LTS branches? Yes if we undefine "vector", we break applications using this syntax. That's a required change for recent rdma-core which uses the name "vector" for another purpose. I don't know what is best/worst.