From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 65526A0527 for ; Mon, 9 Nov 2020 19:42:18 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5EAD2697C; Mon, 9 Nov 2020 19:42:17 +0100 (CET) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by dpdk.org (Postfix) with ESMTP id 133D26883 for ; Mon, 9 Nov 2020 19:42:15 +0100 (CET) Received: by mail-wr1-f49.google.com with SMTP id 23so9867173wrc.8 for ; Mon, 09 Nov 2020 10:42:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=tWlO931QNCvMiMuS3hQerE3CNSyXUnHXIJ/hdBrqCSI=; b=Z62Vw/h68KbjwxVsVrFuA6ROblMk3WqOpcxSk9gBEkZuZvOimumaDvt+ID3ogc0JNG XSglIJHbNIXBr7GRSdrk6oFSx8cGNDgTEvn4W/Od9sxSEmzl603CNOd5KFc33fzBhslP zFmoBXDZB2zU9cmPSloA2qDyt0oGa9sSBJKEZawODTEwtOEkGIELL9eXvLv2g2SW8r0F foHX+aZIv0/oKvhuhd3H72UonNOj1rmYMTg15KCstRslp6siZj9bfCi6RweOCJ4VzdmR yVoZ7NKKPsgHOJl58QWUo6C5QFM+X20l3cvHshGFPU6k2wpwcLUr87GX3ohrOkcLth4x SQHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=tWlO931QNCvMiMuS3hQerE3CNSyXUnHXIJ/hdBrqCSI=; b=D9c0oFTTVd3RUmOMCINfxONA/TTevXqQFUapj23m37YvbIkfnR80dRAbfhcCS1IDQV rt6/HDcqu/PEUGldkFzVx0H3LG1h3/c5yVx4f4p3McSK7HALvzVPz8SRg3+vIOxFHI6+ pfQtX9ewlme/O9Nz273t+jxl+PZD7vXmpjw92CDNXC6DMXXM3dipytjyADw46feaGU79 tz9fY74dvAxRe0vxXSP51LrmOMFWCoseB+esupMhVkVYmv1ykYTf7/cnzenzpT/lhVDx qowNTjOXxPd2kPCJVNS94hAk9kCLYAyOpJW3ErUSjak6RcK9FO18zaTzyJmUSvpqiqzC wKmg== X-Gm-Message-State: AOAM530Ui4Dj27FmkMCLcgJM+arW0IwKP5b4eLS0mpkUo9MXH0UeaIlE iiq8xP36v0/Zi3FEEsGK+iv6swf2Ug8lJw== X-Google-Smtp-Source: ABdhPJyr0Lhvo88IcmDy75ZqibxZkEgyXBygDkVKajRDJtEUoQTMxak48ZZLAAH4lwZ/1ncA+pWy0A== X-Received: by 2002:adf:f2d1:: with SMTP id d17mr3033115wrp.339.1604947334855; Mon, 09 Nov 2020 10:42:14 -0800 (PST) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id g66sm307318wmg.37.2020.11.09.10.42.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Nov 2020 10:42:14 -0800 (PST) From: luca.boccassi@gmail.com To: Arek Kusztal Cc: dpdk stable Date: Mon, 9 Nov 2020 18:40:04 +0000 Message-Id: <20201109184111.3463090-16-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20201109184111.3463090-1-luca.boccassi@gmail.com> References: <20201028104606.3504127-207-luca.boccassi@gmail.com> <20201109184111.3463090-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'doc: remove notice about AES-GCM IV and J0' has been queued to stable release 19.11.6 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 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" Hi, FYI, your patch has been queued to stable release 19.11.6 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 11/11/20. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/bluca/dpdk-stable This queued commit can be viewed at: https://github.com/bluca/dpdk-stable/commit/145749bc13de2fe2f7916b46f425b07fb42a7d5e Thanks. Luca Boccassi --- >From 145749bc13de2fe2f7916b46f425b07fb42a7d5e Mon Sep 17 00:00:00 2001 From: Arek Kusztal Date: Wed, 14 Oct 2020 06:07:00 +0100 Subject: [PATCH] doc: remove notice about AES-GCM IV and J0 [ upstream commit 57e03d2a620534cee72a54396d799a0a6c1ca2d5 ] This patch removes information about deprecation of AES-GCM/GMAC API for IV without J0. Fixes: fac52fb26a54 ("cryptodev: add option to support both IV and J0 for GCM") Signed-off-by: Arek Kusztal --- doc/guides/rel_notes/deprecation.rst | 6 ------ 1 file changed, 6 deletions(-) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index afa94b43e2..c2e1298342 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -67,12 +67,6 @@ Deprecation Notices In 19.11 PMDs will still update the field even when the offload is not enabled. -* cryptodev: support for using IV with all sizes is added, J0 still can - be used but only when IV length in following structs ``rte_crypto_auth_xform``, - ``rte_crypto_aead_xform`` is set to zero. When IV length is greater or equal - to one it means it represents IV, when is set to zero it means J0 is used - directly, in this case 16 bytes of J0 need to be passed. - * sched: To allow more traffic classes, flexible mapping of pipe queues to traffic classes, and subport level configuration of pipes and queues changes will be made to macros, data structures and API functions defined -- 2.27.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2020-11-09 18:40:11.859038676 +0000 +++ 0016-doc-remove-notice-about-AES-GCM-IV-and-J0.patch 2020-11-09 18:40:11.087310598 +0000 @@ -1 +1 @@ -From 57e03d2a620534cee72a54396d799a0a6c1ca2d5 Mon Sep 17 00:00:00 2001 +From 145749bc13de2fe2f7916b46f425b07fb42a7d5e Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 57e03d2a620534cee72a54396d799a0a6c1ca2d5 ] + @@ -10 +11,0 @@ -Cc: stable@dpdk.org @@ -18 +19 @@ -index 22aecf0bab..43e0e09be5 100644 +index afa94b43e2..c2e1298342 100644 @@ -21,3 +22,3 @@ -@@ -132,12 +132,6 @@ Deprecation Notices - will be limited to maximum 256 queues. - Also compile time flag ``RTE_ETHDEV_QUEUE_STAT_CNTRS`` will be removed. +@@ -67,12 +67,6 @@ Deprecation Notices + In 19.11 PMDs will still update the field even when the offload is not + enabled.