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 67603A046B for ; Fri, 23 Aug 2019 11:45:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 55CF81BFA5; Fri, 23 Aug 2019 11:45:01 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id F05621BFA2 for ; Fri, 23 Aug 2019 11:45:00 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 740BF81DE7; Fri, 23 Aug 2019 09:45:00 +0000 (UTC) Received: from rh.redhat.com (ovpn-116-48.ams2.redhat.com [10.36.116.48]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7F4785C226; Fri, 23 Aug 2019 09:44:59 +0000 (UTC) From: Kevin Traynor To: Nipun Gupta Cc: dpdk stable Date: Fri, 23 Aug 2019 10:43:21 +0100 Message-Id: <20190823094336.12078-31-ktraynor@redhat.com> In-Reply-To: <20190823094336.12078-1-ktraynor@redhat.com> References: <20190823094336.12078-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Fri, 23 Aug 2019 09:45:00 +0000 (UTC) Subject: [dpdk-stable] patch 'event/dpaa2: fix timeout ticks' has been queued to LTS release 18.11.3 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.3 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 08/28/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. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable-queue This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable-queue/commit/22b0ecf05f62c8a27ad927cee72266f69b41a882 Thanks. Kevin Traynor --- >From 22b0ecf05f62c8a27ad927cee72266f69b41a882 Mon Sep 17 00:00:00 2001 From: Nipun Gupta Date: Thu, 27 Jun 2019 15:06:04 +0530 Subject: [PATCH] event/dpaa2: fix timeout ticks [ upstream commit aad967bb3c5605d1fb5d6ea81c0c6157eb3e37a0 ] Correct timeout to tick conversion. Fixes: 0ce3ce7c275c ("event/dpaa2: add configuration functions") Signed-off-by: Nipun Gupta --- drivers/event/dpaa2/dpaa2_eventdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/event/dpaa2/dpaa2_eventdev.c b/drivers/event/dpaa2/dpaa2_eventdev.c index 8d168b028..926b7edd8 100644 --- a/drivers/event/dpaa2/dpaa2_eventdev.c +++ b/drivers/event/dpaa2/dpaa2_eventdev.c @@ -641,5 +641,5 @@ dpaa2_eventdev_timeout_ticks(struct rte_eventdev *dev, uint64_t ns, RTE_SET_USED(dev); - *timeout_ticks = ns * scale; + *timeout_ticks = ns / scale; return 0; -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-08-22 19:38:22.469754480 +0100 +++ 0031-event-dpaa2-fix-timeout-ticks.patch 2019-08-22 19:38:20.451026546 +0100 @@ -1 +1 @@ -From aad967bb3c5605d1fb5d6ea81c0c6157eb3e37a0 Mon Sep 17 00:00:00 2001 +From 22b0ecf05f62c8a27ad927cee72266f69b41a882 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit aad967bb3c5605d1fb5d6ea81c0c6157eb3e37a0 ] + @@ -9 +10,0 @@ -Cc: stable@dpdk.org