From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 9FA84A00E6 for ; Tue, 16 Apr 2019 16:37:38 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 911BD1B4D9; Tue, 16 Apr 2019 16:37:38 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 087881B4DC for ; Tue, 16 Apr 2019 16:37:37 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 45766368E3; Tue, 16 Apr 2019 14:37:36 +0000 (UTC) Received: from rh.redhat.com (ovpn-117-214.ams2.redhat.com [10.36.117.214]) by smtp.corp.redhat.com (Postfix) with ESMTP id 20CF71001E92; Tue, 16 Apr 2019 14:37:34 +0000 (UTC) From: Kevin Traynor To: Anoob Joseph Cc: Tejasree Kondoj , dpdk stable Date: Tue, 16 Apr 2019 15:36:20 +0100 Message-Id: <20190416143719.21601-2-ktraynor@redhat.com> In-Reply-To: <20190416143719.21601-1-ktraynor@redhat.com> References: <20190416143719.21601-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Tue, 16 Apr 2019 14:37:36 +0000 (UTC) Subject: [dpdk-stable] patch 'common/cpt: fix null auth only' has been queued to LTS release 18.11.2 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 LTS release 18.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 04/24/19. 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. Thanks. Kevin Traynor --- >From aade391026a6e1581a856d17cffcfa2580ccf6de Mon Sep 17 00:00:00 2001 From: Anoob Joseph Date: Wed, 13 Feb 2019 09:22:50 +0000 Subject: [PATCH] common/cpt: fix null auth only [ upstream commit 3ca687a4a02dedd2469ddd9824bbd531d5828a0c ] Fixes: 351fbee21986 ("common/cpt: support hash") Signed-off-by: Anoob Joseph Signed-off-by: Tejasree Kondoj --- drivers/common/cpt/cpt_ucode.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/common/cpt/cpt_ucode.h b/drivers/common/cpt/cpt_ucode.h index 5933ea77e..d408d50e3 100644 --- a/drivers/common/cpt/cpt_ucode.h +++ b/drivers/common/cpt/cpt_ucode.h @@ -550,5 +550,5 @@ cpt_digest_gen_prep(uint32_t flags, opcode.s.minor = 0x03; /* Send out completion code only */ - vq_cmd_w0.s.param2 = 0x1; + vq_cmd_w0.s.param2 = rte_cpu_to_be_16(0x1); } -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-04-16 15:34:25.310435245 +0100 +++ 0002-common-cpt-fix-null-auth-only.patch 2019-04-16 15:34:25.103181658 +0100 @@ -1,10 +1,11 @@ -From 3ca687a4a02dedd2469ddd9824bbd531d5828a0c Mon Sep 17 00:00:00 2001 +From aade391026a6e1581a856d17cffcfa2580ccf6de Mon Sep 17 00:00:00 2001 From: Anoob Joseph Date: Wed, 13 Feb 2019 09:22:50 +0000 Subject: [PATCH] common/cpt: fix null auth only +[ upstream commit 3ca687a4a02dedd2469ddd9824bbd531d5828a0c ] + Fixes: 351fbee21986 ("common/cpt: support hash") -Cc: stable@dpdk.org Signed-off-by: Anoob Joseph Signed-off-by: Tejasree Kondoj