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 5828446364 for ; Fri, 7 Mar 2025 13:27:09 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 522E04029E; Fri, 7 Mar 2025 13:27:09 +0100 (CET) Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) by mails.dpdk.org (Postfix) with ESMTP id BF1C34029E for ; Fri, 7 Mar 2025 13:27:08 +0100 (CET) Received: by mail-wr1-f54.google.com with SMTP id ffacd0b85a97d-3912d2c89ecso1405079f8f.2 for ; Fri, 07 Mar 2025 04:27:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741350428; x=1741955228; darn=dpdk.org; h=content-transfer-encoding:reply-to:mime-version:message-id:date :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=y4UTwnMvtaLNMAJITVhMbPs6CBVhJdG9hgRIGjrZ7lY=; b=c3g/AfN1iL68PWsopFs0b3Z4SCuCy9+1AwTKoSkKr9tVYZVvpXb+1+aDIBv5ttYbZf 5Co08iRWgxHJysknbtnJFZuuTV9d3G8LuGC4MIVf440h/MPnUCFOzYp9XBwEyUIcjYzm nY+HCSWD4zbQil3f0TmLaNiWjYqcO7Ooqx/4dGCqgt9K/5WXGrkOeFK5ls/GIGNR3YTo qZ1W0PMpm0j/Enpzg3Ub660AKiRNSFYmnsDWGycEMYYIyT792xnHUKikE00oHWr6na2J 8Tl5mdnuZua5Zf7315vT9Dz7kIz5/HTDXTpIUhEZNg9rHAeXGpSeOZht6q1cwdI0rS9L PlMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741350428; x=1741955228; h=content-transfer-encoding:reply-to:mime-version:message-id:date :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=y4UTwnMvtaLNMAJITVhMbPs6CBVhJdG9hgRIGjrZ7lY=; b=FlqD6CimC1LWDp0AFuko+nj2MdJV7AvaH+/WlBFPzdvHPAebfLtOgEde9gBr0kgyrK HyQUJbJ8Vm4+Dp//p6RgqEevyjN6tFFhzfkSCDvHnoH577/rgnNpvfqltH/aXf01yyM5 9wi+Gg+7+clL0zeTngat+a/Eg+rLfxD2pgf/PiSldYmJMV0sZ2AuBAoD/ScE9lF5xeHP PeWruZDH2YEHeZsgHvpTJ2HLyqPBVZ54uczs8WIWifo0sF8DUK0LaYkxe28r2P6nzL1k 6nbIob1kI42P/ngXXOc7Hf0dqSLfII9Rc/24hCK3KW6gq0SNiHAoknpMkaJEzyxjhDEO CJrg== X-Gm-Message-State: AOJu0YxqG8rSwDVH3clpF69C4UIaCBRo7Yukf81Dl58qgjt4j/MHtoHr l+DH4VQlSgwKBxpOH5+fPKCKOySMmFHNDG1+fPgt2gzQ+/rIPlE6u0O3i2ojALg= X-Gm-Gg: ASbGncu2FiXiyAaPbJeaZO/94IDGKaAQEq5Excx/hyvF4t7ndFQwdIC5Y54XHNNaYtQ C8snLIFjMT5lBnvcMPmpgXrXOR46g9H7q381yierPS6KE5Nt0nqdNnGlZvaWVSkGi3/LkZ31z9V 5W9ifD2tz4lONojx16oBVmLcCpymFnHM/g3Ac/TzANGuKBqjJ0stmZ9F0N2FBpC5KX9U5HTW5Ip UA6Qt/gWr4kH8LvhXJsy5IeNgXjg8EeXDfFZJ4CeBb5IZceM4eFC4333VdaZ0O799z6fn94RVU6 qjREamXB3FF9/S8afEN5P5SNeD8xGdSYRWmDF3iUFnrSf+vhPSk= X-Google-Smtp-Source: AGHT+IHJNdZmdV/xZGIRihIWZiDFr6FdXiEL/JSqyNHhbhoP5o+3ERFHtPZvRBw4cHJXPyOEYvHqZA== X-Received: by 2002:a05:6000:4407:b0:38f:2bd4:4f83 with SMTP id ffacd0b85a97d-39132d4f92bmr1548369f8f.16.1741350428043; Fri, 07 Mar 2025 04:27:08 -0800 (PST) Received: from localhost ([2a01:4b00:d036:ae00:ff31:f049:bd38:f7cf]) by smtp.gmail.com with UTF8SMTPSA id 5b1f17b1804b1-43bd426c328sm81221835e9.5.2025.03.07.04.27.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 07 Mar 2025 04:27:07 -0800 (PST) From: luca.boccassi@gmail.com To: dpdk stable Cc: Aaron Conole , Akhil Goyal , Anatoly Burakov , Andre Muezerie , Arkadiusz Kusztal , Chenbo Xia , Fan Zhang , Gowrishankar Muthukrishnan , Jay Zhou , Kai Ji , Long Li , Maxime Coquelin , Michael Santana Subject: please help backporting some patches to stable release 22.11.8 Date: Fri, 7 Mar 2025 12:26:59 +0000 Message-ID: <20250307122702.1415975-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.47.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 22.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 22.11 branch, or - Indicate that the patch should not be backported Please do either of the above by 2025/03/14. You can find the a temporary work-in-progress branch of the coming 22.11.8 release at: https://github.com/bluca/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 22.11] foo/bar: fix baz With git format-patch, this can be achieved by appending the parameter: --subject-prefix='PATCH 22.11' Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". FYI, branch 22.11 is located at tree: https://git.dpdk.org/dpdk-stable Thanks. Luca Boccassi --- 873577fac7 Arkadiusz Kusztal crypto/qat: fix SM3 state size b03cb9c87a Gowrishankar Muthukrishnan vhost/crypto: skip fetch before vring init 57aa3ec91e Long Li net/mana: fix multi-process tracking