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 07AD843CE7 for ; Mon, 18 Mar 2024 16:41:46 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F2918402B8; Mon, 18 Mar 2024 16:41:45 +0100 (CET) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) by mails.dpdk.org (Postfix) with ESMTP id AE59E40289 for ; Mon, 18 Mar 2024 16:41:44 +0100 (CET) Received: by mail-wr1-f41.google.com with SMTP id ffacd0b85a97d-33eee0258abso842152f8f.3 for ; Mon, 18 Mar 2024 08:41:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710776504; x=1711381304; 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=he4zNO2DVnasR3ZMkskrXqbtmCxtvYfVFOvaSYInqRc=; b=Rtalm+K0qPm5FnouRNdbndTpolZFvOjJii60a2OeEEiDh1hf5SIH5RcrtPzLgiCmPm KW7L/PEVylnXeRjvDzcR9SJC3ujiuAAIicau5BlnZrJTS2+aN4IzeIajzMVA2PGvahQO TsBKUZaLwtzOURAwUNyFdeS9Z+RfHuQOab5mS0TMVtwdr7sQsh5WMf0XYc2aEXWG5aak pQzkgdSzOATK0MhnO1zTVNOSmFrb5GkSRIXFwZNWZJ7XBvOG6+nZkbo5sP8H1KcToegx hvVotP/bvTbP2a/k59UC12lUl+9/7xHO7vn37iaNE8MxxmK/W0crNIR9T0Ga3yPJH6K7 Ve0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710776504; x=1711381304; 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=he4zNO2DVnasR3ZMkskrXqbtmCxtvYfVFOvaSYInqRc=; b=AEgcNeNzrIZpC0nXDXquCRrZHn9ABwjujSAPfqwnhaUs+F4jDmMzl0QnB4arUse/Bj Pl4WiPUJavNkcldYR63ZpqXvbUf2zJ3qleYBcJnNb0BZY8bxhuaBtmGSuXSj5CZ2BzyE 0+vbHSN8DAlISA/jM1qlF3eWAmBf5SzP2hktRKeYRAF7PaU5xAChczxY3buxxubs5yCz V9ghP85A8QN4cC2FyCgNmazsWGclkwaZT7yWOx+o8aAOA3gqpyZoHwrQZvJiPh49voOH UqsHYp8icl35Kbqh2pN7Tqgv9AjlHpQYxCqM5aCu8DJLGUgNqmxtourFzNp/nwG0R8kk 1/UQ== X-Gm-Message-State: AOJu0Yy04WtFpqEIrztc0vqcEUY6JkyMdQstpSwUuvRhrDguCAyCzHnI hECX/2altrrzRj2P59MRT9gmFflXbWFsBMgQ4mGSXrF0xLzMs2Khq+xgM3KkpmiGvg== X-Google-Smtp-Source: AGHT+IHrOkejZNHd5Sh7lQXf3svkU1hfEtj1ZTwqS1b8y0MSp6YZEvvhGLFJSqMi5YTYLQ+Kn3dpOw== X-Received: by 2002:a5d:5508:0:b0:33d:a185:17ec with SMTP id b8-20020a5d5508000000b0033da18517ecmr8227951wrv.4.1710776504018; Mon, 18 Mar 2024 08:41:44 -0700 (PDT) Received: from localhost ([2a01:4b00:d036:ae00:7aef:1aaa:3dff:d546]) by smtp.gmail.com with ESMTPSA id n6-20020a5d4006000000b0033e699fc6b4sm10103061wrp.69.2024.03.18.08.41.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 Mar 2024 08:41:43 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Cc: Alexander Kozyrev , Bing Zhao , Dariusz Sosnowski , Gregory Etelson , Matan Azrad , Michael Baum , Ori Kam , Suanming Mou , Viacheslav Ovsiienko , Thomas Monjalon Subject: please help backporting some patches to stable release 22.11.5 Date: Mon, 18 Mar 2024 15:41:37 +0000 Message-Id: <20240318154138.3408560-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/25/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 --- 5ecc8df4fa Dariusz Sosnowski net/mlx5: fix async flow create error handling ff9433b578 Dariusz Sosnowski net/mlx5: fix flow configure validation 727283742a Dariusz Sosnowski net/mlx5: fix rollback on failed flow configure 4359d9d1f7 Gregory Etelson net/mlx5: fix sync meter processing in HWS