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 8FA35A0540 for ; Thu, 7 Jul 2022 10:21:39 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 63A86406B4; Thu, 7 Jul 2022 10:21:39 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id E6EB2406B4 for ; Thu, 7 Jul 2022 10:21:37 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 5345E5C00A3; Thu, 7 Jul 2022 04:21:37 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 07 Jul 2022 04:21:37 -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=1657182097; x= 1657268497; bh=PMkjO55EG/oxkIJXKEexFNzzJPJQtbEeWDQjmxcKPWk=; b=Z 8JPuO2YO3BNdyqdEIyGAvNQx3+oD6fUXtRN57pcFid0+ZvcqhpWWnTZZ2V9topTN MpDXnIeGQBqSpKB5RTtTwJteG4elnrEMmrYHjmV6caPYNpHWsdT0a08hXT8IG2oK YemGGIraFo/pykzaxDe6t/L7SGzyJ3UxQTYQiZztgroYyYlOrLcJRBn6EtPAtZNd WDPRAp9rVuF+/qb5x+Wa5g7/GbjN6u8XFQBjayyVZpWR85E1zwOnMtvjtgrjy8Ye d1xM2orm5YY90+2noz2D1lVyOJw0EHCt5uZHac5eqhV3EZsIjOp3KYHFBQ5AQKDX DXudZyDxZuKW5e9ncIuUA== 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=1657182097; x= 1657268497; bh=PMkjO55EG/oxkIJXKEexFNzzJPJQtbEeWDQjmxcKPWk=; b=w VRpy/HkYGnh3suIvMHjzFexDYJrYRUdw15ekM+0J9eAZYEOKXcqf9BabEI8ttT7s sLgB40i0LjhFIziblzOXyNYFazBxOV7reUpNPEXei6/6YRo0+eKxzBwWrv+99rGZ AQIGm4RB3W8K9+CNxRecdfW3ijfoOdD09pgip2sihRj0i6o32Y6mek+Vo6AWUlCr Lwihbo1N4z/FV5GekXfYcpexPAKTEtbGHVHCSM/GFxdd2VTRMN7dSriIL0O6kiYx ZGfqo/TR1H5YyVlRXeyFhAxE7giq61EYFgpqAZmvsG3fgpxbMox7SwIb7x4yxzgR rz5calfS91v9p6YFWjY+Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeihedgtdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 7 Jul 2022 04:21:36 -0400 (EDT) From: Thomas Monjalon To: Christian Ehrhardt Cc: "Xueming(Steven) Li" , Luca Boccassi , Kevin Traynor , "stable@dpdk.org" Subject: Re: [19.11][20.11][21.11] ppc64 fixes backport Date: Thu, 07 Jul 2022 10:21:34 +0200 Message-ID: <14890598.ov1OQ5z9iq@thomas> In-Reply-To: References: <6239212.097qLLJo0e@thomas> 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 07/07/2022 09:44, Christian Ehrhardt: > On Thu, Jul 7, 2022 at 8:51 AM Thomas Monjalon wrote: > > > > 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. > > It is ok for new DPDK releases to add this, but not for LTS backports. > > In general LTS releases are usually updated and rebuild against their > own older environment. > So if "new rdma-core" is a problem it only is a problem for "new DPDK". > > IMHO LTS versions of DPDK should not take such a change. OK