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 5968BA0540 for ; Wed, 6 Jul 2022 20:53:20 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2A88F40691; Wed, 6 Jul 2022 20:53:20 +0200 (CEST) Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) by mails.dpdk.org (Postfix) with ESMTP id 43E0D40691 for ; Wed, 6 Jul 2022 20:53:19 +0200 (CEST) Received: by mail-ej1-f54.google.com with SMTP id lg18so8840344ejb.0 for ; Wed, 06 Jul 2022 11:53:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QtOxRMPc3DV096KQj/71gATcoBfwXgrTtlfTKOHrnl8=; b=LDlEKce0vvEg4Ul2SevXm5/QGSA418JfiqrTGmDQfxnbOaE+jrMGyvJCX5rxwAjTjm KTjVo455g7tcmssj6giAEt01hXzLQLwGzCo44mTtU2z4xBRIu6Qzlh4FuxsbQXjkeLeq DXuW01y2zhijEjrdCv9zPacvBQF0adqivVrQrr/a+YRYWLsc5C8/pQAk1YUuG+yw5fX4 qqE/g2o4e4yawFlYJIuHSGhkaK+IdnfbcQpoRxyd7hftjvtL46PwOSoukaGA8DedC/vB C8lqzlyZoBYS9W6FolbEZqcKkRXuGhxMo2ZxtW4Gnbejglq//zWzXJZueGnGrgU9ja02 0+0Q== X-Gm-Message-State: AJIora8UEpaVfoyAUAvQ3xyf1uszlns32Sm0f4fJGkeupiy7nwyxst1b DpPAI1zpd0I69kCWWflY7VDjPVVGzkAAEw== X-Google-Smtp-Source: AGRyM1svlaPEMLsq5nNg8jYh3+OnLjuJmIAoFJN6fjg7/eOk4iQKyAvPof8BBLjA7u2IfvsNWuuSKQ== X-Received: by 2002:a17:907:c1d:b0:726:3239:fe83 with SMTP id ga29-20020a1709070c1d00b007263239fe83mr41549589ejc.51.1657133598738; Wed, 06 Jul 2022 11:53:18 -0700 (PDT) Received: from mail-ed1-f51.google.com (mail-ed1-f51.google.com. [209.85.208.51]) by smtp.gmail.com with ESMTPSA id d10-20020a17090648ca00b0070b8a467c82sm17619880ejt.22.2022.07.06.11.53.18 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jul 2022 11:53:18 -0700 (PDT) Received: by mail-ed1-f51.google.com with SMTP id v12so7784985edc.10 for ; Wed, 06 Jul 2022 11:53:18 -0700 (PDT) X-Received: by 2002:a05:6402:695:b0:435:65f3:38c2 with SMTP id f21-20020a056402069500b0043565f338c2mr33103527edy.347.1657133598438; Wed, 06 Jul 2022 11:53:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Luca Boccassi Date: Wed, 6 Jul 2022 19:53:07 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [19.11][20.11][21.11] ppc64 fixes backport To: "Xueming(Steven) Li" Cc: Kevin Traynor , "christian.ehrhardt@canonical.com" , "stable@dpdk.org" , "NBU-Contact-Thomas Monjalon (EXTERNAL)" Content-Type: text/plain; charset="UTF-8" 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 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? Kind regards, Luca Boccassi