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 9D7E1A0A0A for ; Thu, 3 Jun 2021 07:46:12 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 638EF4067A; Thu, 3 Jun 2021 07:46:12 +0200 (CEST) Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by mails.dpdk.org (Postfix) with ESMTP id 18DD34067A for ; Thu, 3 Jun 2021 07:46:11 +0200 (CEST) Received: from mail-qv1-f69.google.com ([209.85.219.69]) by youngberry.canonical.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1logBG-0004mF-Iy for stable@dpdk.org; Thu, 03 Jun 2021 05:46:10 +0000 Received: by mail-qv1-f69.google.com with SMTP id v19-20020a0ce1d30000b02902187ed4452eso3667507qvl.6 for ; Wed, 02 Jun 2021 22:46:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FHt8/TtD6sdjhVHB5e2bvAIhX1zPg/f37EzF5db40gY=; b=lCNHi7uEq4BZre8GUsdV5SKCGjv/nes8shdC0UoIh8FcesZDjJs+fE6nL+J2U4eyVR 4EsgQKwigY8PjmRduBCMHJ+33kwp6NPsNOU3c4KCyyBu+NXBFjXXujjDQ8oaL6Rf2cao 5Z+P/KaWnRx8FQAE4wSNVUhMrZKCfO0UoeV5aE0v8NV+Saz0lSnzoWCaWPpRTaY866u6 VBkVHVw88fdq8C2X1eIujwYTv6FOsOG7ZigModMvt0ms2BsKPIAS8vX/CVIPgAbhlssQ S5qS5bD8TA8o4oSGzCFpVlo77fcWWONtzK7iM0GYtgUNyKHB/IJbgbMfVERw+ZlgOUpk q1Gw== X-Gm-Message-State: AOAM533CkgQ7AU7xzPF4Ra4SksgeF1jib/K0SDpzFJlU2FC9tgKajSsA zS6jZHncv4x9TlMJqMXBiWgw/2UdhYNYJVf+a7wtJ5ya6kyTVE25Qp1R3RA8jPYeYYhRxCP2Q/Z Gy+6BYyodFGKF856/BpTKe54aym3nmSTXPugesc/L X-Received: by 2002:ad4:5bef:: with SMTP id k15mr31272453qvc.22.1622699169781; Wed, 02 Jun 2021 22:46:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwj2G2j5atvWIEcQv2ZE6TRDIjGDaA90VUgTl52e9V+bXgTt3TxCiluPhJc9ZUI7HwI8uSuS9NXOpXyI7amm9M= X-Received: by 2002:ad4:5bef:: with SMTP id k15mr31272446qvc.22.1622699169591; Wed, 02 Jun 2021 22:46:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Christian Ehrhardt Date: Thu, 3 Jun 2021 07:45:43 +0200 Message-ID: To: Hemant Agrawal Cc: dpdk stable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-stable] 19.11 - dependencies of 22629f05 "crypto/dpaa_sec: affine the thread portal affinity" not fulfilled 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 Sender: "stable" On Wed, Jun 2, 2021 at 5:04 PM Hemant Agrawal wrote: > > I will be submitting a patch in next 1-2 days. Thanks in advance! I was collecting a few more changes for a 19.11.9-rc2 today, but I do not want to tag a release candidate every day. So I'm waiting for your changes to show up (or you telling me that it won't be backported). It would be great if those could be available *tomorrow morning to be able to tag rc2 before this week is over. * = my tomorrow morning so ~23h from the time I sent this email :-) > - Hemant > > > -----Original Message----- > > From: Christian Ehrhardt > > Sent: Tuesday, June 1, 2021 12:43 PM > > To: Hemant Agrawal > > Cc: dpdk stable > > Subject: 19.11 - dependencies of 22629f05 "crypto/dpaa_sec: affine the > > thread portal affinity" not fulfilled > > > > Hi Hemant, > > this commit was targeted for the stable releases: > > > > commit 22629f05f8832358d01872414e0e30c2c81e43d4 > > Author: Hemant Agrawal > > Date: Mon May 3 14:09:53 2021 +0530 > > > > crypto/dpaa_sec: affine the thread portal affinity > > > > But prior to 20.08 the following change was not present. > > > > commit e58722218aa9ad6b527423f8b95e788e6c5a15b7 > > Author: Rohit Raj > > Date: Tue Jul 7 14:52:27 2020 +0530 > > > > drivers/dpaa: optimize thread local storage > > > > That leads to compile errors and seems not trivial to backport as changes to > > local storage could have various dependencies and implications that I might > > miss. > > > > If you want the patch applied to 19.11 I'd ask you to have a look and provide > > a backport for it that considers all that and is tested. > > Otherwise please feel free to just let me know that 19.11 series will be fine > > without 22629f05. > > > > -- > > Christian Ehrhardt > > Staff Engineer, Ubuntu Server > > Canonical Ltd -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd