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 71E2148BAC for ; Tue, 25 Nov 2025 19:11:43 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6C71E40615; Tue, 25 Nov 2025 19:11:43 +0100 (CET) Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) by mails.dpdk.org (Postfix) with ESMTP id C395640615 for ; Tue, 25 Nov 2025 19:11:42 +0100 (CET) Received: by mail-wm1-f41.google.com with SMTP id 5b1f17b1804b1-477a219db05so34739505e9.2 for ; Tue, 25 Nov 2025 10:11:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764094302; x=1764699102; 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=jEsGRrp+XBc60aHbOTOtDQQRy8GLkF5q/538jS57sMo=; b=QInxHw1XmGQ1Ncd9ZPzY7CJWKSqYm0CxWkDh3GBPgVnqYq3dcVweM4hTLa1UpCiL3l 0McN7EyTvyebtvUvaAj3PsLX9KthkX4LPxpbUxtLESqGW9y+FwUXPwY5CgJZN4z/FWZb 9K5/VfRQS8k7dC4HAqtn9Cw0WG54/BRYbn5wGptcil0INvbO4PTM2Gb1fLbgU211Mrq6 /f88ygSYkrUXlg0XYpCjSjVKEl4ZesT8iZxlg3SGHVW9AWeLdFw57VZ824D8Mf6CpNhw q7gpdKBZXYW1Nlx20jZwgtAtbBuvTnyeuCDxDWsLTF7mHDXbCuuWDkjC08vAOeKA31IT pBiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764094302; x=1764699102; h=content-transfer-encoding:reply-to:mime-version:message-id:date :subject:cc:to:from:x-gm-gg:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=jEsGRrp+XBc60aHbOTOtDQQRy8GLkF5q/538jS57sMo=; b=evhobjbwOq6K3onM5W1yOTROs28R11XTrAdmKio/0A9vx4oQU875rTBkNHqxEY5nz4 hOF49sGfIVIeZ7oJfBH3a2JTfUNkHjWu9gGYQx7ClAnBES2qb2JpBt4kDQhgxI3fhvpW EIA/BKI6kTrdIwP2lcZoKDUJs7rmzjcDqSUpM6G7oCT+kSi9hQTVl8242u1H6bTL+yE8 wh3L+4+UdIBQBNMYxQ0hpZrSUlS5JCuOSbeOQaXgC4xSKkmS+02zIzrmJIflZGKDOgnp 9GWH35+9uzgGHhE7MtUkLXF5Z3c6Usf0G/h359H7s5KJjgoVHQSFUXpJD6GJdLMINh3g 5oNg== X-Gm-Message-State: AOJu0YyH46UmbZsCVczqYOJ5Kb1WEGQ4voOOe9abrgyPoNQwEWahEVVX F7VWDKRRCZF1MJb/HFR7Am7PNOXXxWnNs5FK2ZZL0cKraWA2NsB7oNPp7qe4Ag== X-Gm-Gg: ASbGncse+WYl7Hhc5ZsFxZnsGysCYeDO7ZHrWEpkAmwqSqhha2XKweo3PJo2M9pQkPH Tz6K7AvallGWJlshvCi3+1P/llKjtb5HHXKYa1N1DxBNVQIEbygF2oynG+q/sgd8YOORPWRT4Gs I+7X6INkteMClFmufVxGRoRJdiewbtIMuoaRPDz7qv683CmWxsaKejuQRtUHXo8jJ3Fz7fCYRxy JC0oEKJmatUIp+8D4a+0sgWebuOJfDbBRXcFjIqOGFEddO9D/lwMT7iBcIL0kEDXA0Ljxo0RLbC v+qRHO6plNXho8KMz60WA2yuuI4YTHc+foiVi7DFtrM7MeeOemce7MVO69l+s+ddhd5ReA1BWoH tLFJ6MiqhspaMZIVGmH5WfY+N618L9JYwghL3a0ALhXWuPMHpzjDGIJCVwO48kMAj7i1qD1jXFO vN6w== X-Google-Smtp-Source: AGHT+IGPEswchnQl4fDl5lbXWd7b2IdG5vZMLePHn1rcO12nGfTCzFcVSnBw2S7VMvmMPtPT5KuKhA== X-Received: by 2002:a05:600c:310f:b0:475:de14:db1e with SMTP id 5b1f17b1804b1-477c1125568mr196217245e9.24.1764094302144; Tue, 25 Nov 2025 10:11:42 -0800 (PST) Received: from localhost ([2a01:4b00:d036:ae00:e128:6b49:7104:a117]) by smtp.gmail.com with UTF8SMTPSA id 5b1f17b1804b1-4790530113esm20734525e9.14.2025.11.25.10.11.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Nov 2025 10:11:41 -0800 (PST) From: luca.boccassi@gmail.com To: dpdk stable Cc: Dariusz Sosnowski , Matan Azrad , Viacheslav Ovsiienko Subject: please help backporting some patches to stable release 22.11.11 Date: Tue, 25 Nov 2025 18:11:35 +0000 Message-ID: <20251125181137.1784048-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.47.3 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/12/01. You can find the a temporary work-in-progress branch of the coming 22.11.11 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 --- a2234609bf Viacheslav Ovsiienko net/mlx5: fix flex flow item header length