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 BC18946BD9 for ; Mon, 21 Jul 2025 18:06:25 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B09D940297; Mon, 21 Jul 2025 18:06:25 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 4216640297 for ; Mon, 21 Jul 2025 18:06:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1753113983; 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=pGrUKcwGaS0pzN6CvuY/ui26iUVrd7GSMYnCWujyeHc=; b=gW0F+Uir2pN40AD/VVGFNaFjixheNJSHoXoyqVylA8JY95PtIu5mVNfmhyYX9v9533Uqke xmLCsQ877orkzJmvwyjU75R0r7Jpi6GZN/DZGD4V8tjjRo4UzPgecUqhdAgcL9ER6B31j3 3446jumeL0zNubuLymG51xZbl2gvGwY= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-104-Rbi_1rcrPj-GL-8K1ubJAw-1; Mon, 21 Jul 2025 12:06:21 -0400 X-MC-Unique: Rbi_1rcrPj-GL-8K1ubJAw-1 X-Mimecast-MFC-AGG-ID: Rbi_1rcrPj-GL-8K1ubJAw_1753113979 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (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-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 0ADA2195608C; Mon, 21 Jul 2025 16:06:19 +0000 (UTC) Received: from rh.Home (unknown [10.45.224.14]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id CBF66195608D; Mon, 21 Jul 2025 16:06:12 +0000 (UTC) From: Kevin Traynor To: dpdk stable Cc: Akhil Goyal , Anatoly Burakov , Bruce Richardson , Dengdui Huang , Huisong Li , Jerin Jacob , Jie Hai , Kiran Kumar K , Nithin Dabilpuram , Nithinsen Kaithakadan , Rajesh Mudimadugula , Sunil Kumar Kori , Tejasree Kondoj Subject: please help backporting some patches to stable release 24.11.3 Date: Mon, 21 Jul 2025 17:06:03 +0100 Message-ID: <20250721160605.78292-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: MQ8zAh_x_qEwoszCWvhMHnw1W6Mwdgku_XWmN4g6Nqw_1753113979 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 07/28/25. You can find the a temporary work-in-progress branch of the coming 24.11.3 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 --- b4ce09b852 Bruce Richardson net/ixgbe/base: fix lock checker errors 25e35296b5 Sunil Kumar Kori net/cnxk: fix reconfiguring MAC address 9843181aa5 Rajesh Mudimadugula crypto/virtio: fix driver ID a1efd31b0f Nithinsen Kaithakadan common/cnxk: fix AES-CTR salt handling 99c065da47 Dengdui Huang net/hns3: fix Rx packet without CRC data 98cf04bb90 Kiran Kumar K test/graph: fix second run 4cd8c72f66 Bruce Richardson net/ice: fix inconsistency in Rx queue VLAN tag placement (struct ci_rx_queue does not exist in 24.11)