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 1593E43CAD for ; Thu, 14 Mar 2024 01:17:21 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EB599427E3; Thu, 14 Mar 2024 01:17:20 +0100 (CET) Received: from mail-wr1-f50.google.com (mail-wr1-f50.google.com [209.85.221.50]) by mails.dpdk.org (Postfix) with ESMTP id 419E140297 for ; Thu, 14 Mar 2024 01:17:19 +0100 (CET) Received: by mail-wr1-f50.google.com with SMTP id ffacd0b85a97d-33e570ef661so151539f8f.1 for ; Wed, 13 Mar 2024 17:17:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710375438; x=1710980238; 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=s2o02xt03NYU1DMulMs9hGCVOtADnYBZiMZXdjLpwDs=; b=Wpz3ACXdy9gVAt5zn2gXF8exy1wyHVpkG9nIBwZVRKv8CurGds3VCaL+E/NQ8o1v5O /G3lXF13j12LWg+Kqs26XoOZOByURsMPZ+dAccCnw+2aqopvb3iWPvJJMZmST/81mA7k CEvif5kvKcd0Q11ZbGcITusR9eqOeTjrCxR/BXDjwZrQF5P/5YOD6M2Y42u/Ng7Xjwv+ EirZ3f+RzopxC3YWXg91pnjKFHVpRN9stWw0RosPUNnYFZ7PvIoA43UgEXb/Df6c/yWh SKPfAMcQP8HvBb4OQkUnrEFaTJRAJBRU6oLgg0sTpUfcxA8ijNQIyNWlz3sYQyqLBJxo GPMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710375438; x=1710980238; 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=s2o02xt03NYU1DMulMs9hGCVOtADnYBZiMZXdjLpwDs=; b=rlO9l1XSuGQ6fYOxvbDzhhOs0DYWFImB6iNfXYE4AnlRmbEYy+nn0Z9gZg0E1Wy0hG bDpFXLtRmY7d5Rjc2/XMfqvWB6KrfvZTVqrpUEBUENf3XTxSwzZzu0g6br11Abg511I2 pJ3pYqRZ1iqazMOL3fgs0cvD/jG5tZvZDQBWVSrZ2lE2ZUW2ZZbfHujXFxrfSO1sD5k2 BhHndGIW4gU/gnzJOBk3QA92+1ws+w7GDFJylDLO7nffXCmfQ5a2lXck/loeBojjm4gZ gIiGOcfmXAW47RR/hpwq5++BZk9b1lX0ItJ7fokReofijofxEhXUn8nm0/JdTPQuz8Td IIxw== X-Gm-Message-State: AOJu0Yx+k7ME6D1F3pCl4yDJU6soZK15tekKXnJg8cMW4+ka7/VddDdT WoWWM/X/GF90hh5RZRcrh0425R2UYLlP4uTZGzkuye2eXUyLBn36mOkeTvob9PQ= X-Google-Smtp-Source: AGHT+IHOz8MyDip3k9YRL8LRrlWH/eKqGXFjt4qNaeEuxVWu94NUUIkUhCL2LPa9HW+GW+brYVIp1A== X-Received: by 2002:adf:a154:0:b0:33e:c34f:20a7 with SMTP id r20-20020adfa154000000b0033ec34f20a7mr88194wrr.48.1710375438488; Wed, 13 Mar 2024 17:17:18 -0700 (PDT) Received: from localhost ([137.220.120.171]) by smtp.gmail.com with ESMTPSA id q20-20020adfcb94000000b0033dedd63382sm289455wrh.101.2024.03.13.17.17.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Mar 2024 17:17:18 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Cc: Alex Vesker , Bing Zhao , Dariusz Sosnowski , Erez Shitrit , Itamar Gozlan , Kiran Kumar K , Matan Azrad , Nithin Dabilpuram , Ori Kam , Pavan Nikhilesh , Rahul Bhansali , Satha Rao , Sunil Kumar Kori , Viacheslav Ovsiienko , Xiaoyu Min Subject: please help backporting some patches to stable release 22.11.5 Date: Thu, 14 Mar 2024 00:17:12 +0000 Message-Id: <20240314001712.2812443-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.39.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 03/21/24. You can find the a temporary work-in-progress branch of the coming 22.11.5 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 --- d755221b77 Dariusz Sosnowski net/mlx5: fix flow counter cache starvation e23edbc509 Itamar Gozlan net/mlx5/hws: skip item when inserting rules by index 3232c95d2c Nithin Dabilpuram net/cnxk: fix indirect mbuf handling in Tx