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 9C9F346364 for ; Fri, 7 Mar 2025 13:48:17 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 95FEC40E41; Fri, 7 Mar 2025 13:48:17 +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 BEE0640E30 for ; Fri, 7 Mar 2025 13:48:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1741351695; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=OHqg3pYf7CI3iCRVlrLRSzWPZiN64qZ19ptrCZ1CvHA=; b=U6avxzf65D5iwvBgQgd3Hs7LGogYJsTXSX32aws92e9lPWO1rq77P4Yzbp9zvgIDUk5Yc8 VfIkH4QVc7ruQ1IRReFDW6LiHjTAQ1eDn8MqF2IcIa/KjDxnb3fCGV8PeaF5JKS+HGSRls HS+0YvZZqbdhc5X1pB4h1TbenEedTi4= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-517-SnfN2ZfbPIWzKLCscHmzaQ-1; Fri, 07 Mar 2025 07:48:14 -0500 X-MC-Unique: SnfN2ZfbPIWzKLCscHmzaQ-1 X-Mimecast-MFC-AGG-ID: SnfN2ZfbPIWzKLCscHmzaQ_1741351693 Received: from mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 1B12A180AF53; Fri, 7 Mar 2025 12:48:13 +0000 (UTC) Received: from rh.Home (unknown [10.45.226.25]) by mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 4ACCA1956095; Fri, 7 Mar 2025 12:48:11 +0000 (UTC) From: Kevin Traynor To: Gowrishankar Muthukrishnan Cc: Akhil Goyal , Maxime Coquelin , dpdk stable Subject: patch 'examples/vhost_crypto: fix user callbacks' has been queued to stable release 24.11.2 Date: Fri, 7 Mar 2025 12:46:51 +0000 Message-ID: <20250307124726.475001-18-ktraynor@redhat.com> In-Reply-To: <20250307124726.475001-1-ktraynor@redhat.com> References: <20250307124726.475001-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.15 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: _XUHQLmjY6AJFpzr1jIZ4YbKwkZH5GxgAkkoINXHc6M_1741351693 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true 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 Hi, FYI, your patch has been queued to stable release 24.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 03/12/25. 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 This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/be573724610a824164dd6b775e7fe97d131722bd Thanks. Kevin --- >From be573724610a824164dd6b775e7fe97d131722bd Mon Sep 17 00:00:00 2001 From: Gowrishankar Muthukrishnan Date: Fri, 28 Feb 2025 19:17:11 +0530 Subject: [PATCH] examples/vhost_crypto: fix user callbacks [ upstream commit f7cf44d49b1115238a87c5852db4b47290bfdc25 ] In order to handle new vhost user connection, use new_connection and destroy_connection callbacks. Fixes: f5188211c721 ("examples/vhost_crypto: add sample application") Signed-off-by: Gowrishankar Muthukrishnan Acked-by: Akhil Goyal Reviewed-by: Maxime Coquelin --- examples/vhost_crypto/main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/vhost_crypto/main.c b/examples/vhost_crypto/main.c index 558c09a60f..b1fe4120b9 100644 --- a/examples/vhost_crypto/main.c +++ b/examples/vhost_crypto/main.c @@ -363,6 +363,6 @@ destroy_device(int vid) static const struct rte_vhost_device_ops virtio_crypto_device_ops = { - .new_device = new_device, - .destroy_device = destroy_device, + .new_connection = new_device, + .destroy_connection = destroy_device, }; -- 2.48.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-03-07 11:02:57.563959084 +0000 +++ 0018-examples-vhost_crypto-fix-user-callbacks.patch 2025-03-07 11:02:56.858353772 +0000 @@ -1 +1 @@ -From f7cf44d49b1115238a87c5852db4b47290bfdc25 Mon Sep 17 00:00:00 2001 +From be573724610a824164dd6b775e7fe97d131722bd Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit f7cf44d49b1115238a87c5852db4b47290bfdc25 ] + @@ -10 +11,0 @@ -Cc: stable@dpdk.org