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 4E9E148BFA for ; Mon, 1 Dec 2025 15:55:47 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4703E4021F; Mon, 1 Dec 2025 15:55:47 +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 8D7DF4021F for ; Mon, 1 Dec 2025 15:55:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1764600945; h=from:from:reply-to: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; bh=Hhz4TbYb+U3cdneyN8SdAkpUVpgsvtq4oHYaD0/QF/c=; b=Ij4wmul9OHZOxIywUdxfwj1fFE/nJtClFiK+IWj5DCLdNxcp7FtdlhUXGOeXjyWPa3ZYb4 6AAxnrXSnbQh+MyvZM9tK1aGuf0bDY36sRztusz1RgG8eFy9I5LAN6GJzO+0X1bzdmk5Ky DyNdjMYsbKdbRwYp/wFOsgwyGA2j0K0= 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-137-sBRquWfPMCSiGtUSKzs07w-1; Mon, 01 Dec 2025 09:55:39 -0500 X-MC-Unique: sBRquWfPMCSiGtUSKzs07w-1 X-Mimecast-MFC-AGG-ID: sBRquWfPMCSiGtUSKzs07w_1764600936 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (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 5CBE3180047F; Mon, 1 Dec 2025 14:55:35 +0000 (UTC) Received: from rh.redhat.com (unknown [10.42.28.204]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 41B9519560A7; Mon, 1 Dec 2025 14:55:29 +0000 (UTC) From: Kevin Traynor To: dpdk stable Cc: Anatoly Burakov , Bruce Richardson , Dariusz Sosnowski , Dhruv Tripathi , Gagandeep Singh , Hailin Xu , Honnappa Nagarahalli , Jerin Jacob , Konstantin Ananyev , Monendra Singh Kushwaha , Nithinsen Kaithakadan , Ola Liljedahl , Pavan Nikhilesh , Sunil Kumar Kori , Viacheslav Ovsiienko , Wathsala Vithanage Subject: please help backporting some patches to stable release 24.11.4 Date: Mon, 1 Dec 2025 14:55:22 +0000 Message-ID: <20251201145523.633988-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: W7O-QrRUPoiWDDT9c6pb8EtEk3vWqqsZ5Kci0dwOpY8_1764600936 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: , Reply-To: dpdk stable Errors-To: stable-bounces@dpdk.org Hi commit authors (and maintainers), Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh I didn't apply following commits from DPDK main to 24.11 stable branch, as conflicts or build errors occur. Can authors check your patches in the following list and either: - Backport your patches to the 24.11 branch, or - Indicate that the patch should not be backported Please do either of the above by 12/04/25. You can find the a temporary work-in-progress branch of the coming 24.11.4 release at: https://github.com/kevintraynor/dpdk-stable It is recommended to backport on top of that to minimize further conflicts or misunderstandings. Some notes on stable backports: A backport should contain a reference to the DPDK main branch commit in it's commit message in the following fashion: [ upstream commit ] For example: https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb When sending the backported patch, please indicate the target branch in the subject line, as we have multiple branches, for example: [PATCH 24.11] foo/bar: fix baz With git format-patch, this can be achieved by appending the parameter: --subject-prefix='PATCH 24.11' Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". FYI, branch 24.11 is located at tree: https://git.dpdk.org/dpdk-stable Thanks. Kevin --- f2f75ffe14 Viacheslav Ovsiienko net/mlx5/hws: fix ESP header match in strict mode 08b83e84e1 Nithinsen Kaithakadan crypto/cnxk: fix TLS mbuf 8a8c02d2bb Anatoly Burakov vfio: fix custom containers in multiprocess 0e3c389b9e Gagandeep Singh bus/dpaa: do proper cleanup of frame queues on shutdown 3bf9f0f9f0 Viacheslav Ovsiienko net/mlx5: fix control flow leakage for external SQ a4ad0eba9d Wathsala Vithanage ring: establish safe partial order in default mode 66d5f96278 Wathsala Vithanage ring: establish safe partial order in HTS mode 36b69b5f95 Wathsala Vithanage ring: establish safe partial order in RTS mode 743bbd3bd2 Sunil Kumar Kori net/ice: fix Tx packet prepare 19d7188f6f Bruce Richardson net/ixgbe: fix Tx packet prepare bd96307d15 Bruce Richardson net/fm10k: fix Tx packet prepare 5a753913e0 Monendra Singh Kushwaha common/cnxk: fix inline device write operation 3e48adc135 Pavan Nikhilesh event/cnxk: fix Rx offload flags