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 B7836423FA for ; Tue, 17 Jan 2023 09:11:05 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A62C940151; Tue, 17 Jan 2023 09:11:05 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id CD498400D4 for ; Tue, 17 Jan 2023 09:11:04 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1673943064; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=878QWEwYSojViCj2ObDtuTqHp/eXsS6gPDd1tOIlRM4=; b=YbSWa/4okjBN7jF/NQhSTIphC9tYoOu/Uo/N/KPfMjC9b8lyk/jwheWuz2ecorMEQqXIuf zRStX3BWncRJEVMd0S+rqA8BN7h7uXBxRtgIcf9AAKR0MP1+vY08HxPGyAmmYk4CUqFQvV KQs1CPmxUjDMhx9wFDcMhexgKNdxUx0= Received: from mail-pj1-f72.google.com (mail-pj1-f72.google.com [209.85.216.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-1-iJTxyoQOPsC8ZUM7RiYRug-1; Tue, 17 Jan 2023 03:11:02 -0500 X-MC-Unique: iJTxyoQOPsC8ZUM7RiYRug-1 Received: by mail-pj1-f72.google.com with SMTP id s22-20020a17090aad9600b002271d094c82so15226738pjq.7 for ; Tue, 17 Jan 2023 00:11:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=878QWEwYSojViCj2ObDtuTqHp/eXsS6gPDd1tOIlRM4=; b=zFnLeQ9vxsS6UJraQrfQDp1XrrfWadgyxwTU2JMgkaOG465Wo011G1Ek5krVymlqHg iuQyiZXdKChVKVGT1fPNTQ0HX4A3onQpTaVqiitBLoVUqcY/D/2bCBsgdzGUsv7BdI4Z pIGePxSSDTqU0i08ALs3v5vjX7EHKrBD67jvEh/1DhriXiRu/X3v+li+CPSK0MD6ZJ7V 46Z7mSlbO/JBUvUhzvBLdUO/cvyGDzezVsITn8AIFRIpJYgt8I0DAJ80zXpklHEvyTL+ 1j7Q33qx0uxVKMAUdv0F3boqqz+TbDxr/Bwi1cPPwCWyVRYgSzb3zgsQxFXSgOwb1a9I FM0w== X-Gm-Message-State: AFqh2krz8qG1NWCsHyUgZIkPWTnppokcphR/hIyslpeYf95vmgV4jUPw GebcGiy/wpY5gsMH/UpD3Gvj1Tk72h2rQwW8j+GZgo974Xpbj1gyROjUQfNaQVg4NLJIbPyyOJ/ eM/8f1P07vrcPzFu5th36GLA= X-Received: by 2002:a17:90b:3711:b0:226:197:63fd with SMTP id mg17-20020a17090b371100b00226019763fdmr172172pjb.55.1673943061920; Tue, 17 Jan 2023 00:11:01 -0800 (PST) X-Google-Smtp-Source: AMrXdXuHKF487CdF7m9x3++RLkWUhyQS9l+3SIFT7C9UlY7/QDRb7WAzTFtsox3u+p1b4eqP7mv3NqOTtPtYW+dgffk= X-Received: by 2002:a17:90b:3711:b0:226:197:63fd with SMTP id mg17-20020a17090b371100b00226019763fdmr172167pjb.55.1673943061695; Tue, 17 Jan 2023 00:11:01 -0800 (PST) MIME-Version: 1.0 References: <20230109103436.996994-1-david.marchand@redhat.com> In-Reply-To: From: David Marchand Date: Tue, 17 Jan 2023 09:10:50 +0100 Message-ID: Subject: Re: [PATCH] crypto/qat: fix build for generic x86 with GCC 12 To: Akhil Goyal , Kai Ji Cc: dev@dpdk.org, stable@dpdk.org, Ciara Power , Fan Zhang , Bruce Richardson X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com 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 Tue, Jan 10, 2023 at 12:27 PM Bruce Richardson wrote: > > On Mon, Jan 09, 2023 at 11:34:36AM +0100, David Marchand wrote: > > Similar to commit 04361fe2aca8 ("crypto/qat: fix build with GCC 12"). > > The issue appears when building with the "generic" target we have in > > devtools/test-meson-builds.sh. > > > > Fixes: 3227bc7138f5 ("crypto/qat: use intel-ipsec-mb for partial hash and AES") > > Cc: stable@dpdk.org > > > > Signed-off-by: David Marchand > > --- > > drivers/crypto/qat/qat_sym_session.c | 2 ++ > > 1 file changed, 2 insertions(+) > > > Confirm that this fixes the build issue. > > Tested-by: Bruce Richardson > No objection from maintainer, Akhil, can you take this to next-crypto? Thanks. -- David Marchand