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 2642745BB6 for ; Wed, 23 Oct 2024 23:31:59 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F35D340261; Wed, 23 Oct 2024 23:31:58 +0200 (CEST) Received: from mail-wm1-f51.google.com (mail-wm1-f51.google.com [209.85.128.51]) by mails.dpdk.org (Postfix) with ESMTP id 8DEAE40261 for ; Wed, 23 Oct 2024 23:31:57 +0200 (CEST) Received: by mail-wm1-f51.google.com with SMTP id 5b1f17b1804b1-4315baa51d8so2265595e9.0 for ; Wed, 23 Oct 2024 14:31:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729719117; x=1730323917; 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=ZBjUCHcuclfDzA+DsrR3dsb8lyKnY4iiP1Xh5xT9+Ck=; b=ZiFSvmi/lbD5rL92FSaSckju9JkpD7nMeDBpruQa6V+0vnKovoTr6QcmJOaYVlNgWb dBRI68xzNXtSq6Ip76UXVqjcTGUNbUdWbhjLjUYGs/3IpZhyX1EjwC5sScT1Ao1TCs+Z 8T9w6oB6kJxnfTCRJbNls3p1eDULJhecO6H+RI1HJMGQ3bIyIs3vznKhnrgjq9A0PpYi /pZ5nNucSOZR8rHqvbuS7eD6XGo+mqcZLiAjH4543zUyP1/zDeWjZAETIxUwAlBqTID2 Enz2TTiQYLKucy64x/Uz0P8UO8TDyALb1h+rtibB7ayqTaDQ2KN2ZfU5XbPVZmiDc0NI 0I+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729719117; x=1730323917; 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=ZBjUCHcuclfDzA+DsrR3dsb8lyKnY4iiP1Xh5xT9+Ck=; b=lZpQjCXeu/kW4S12Hgze0nkbV9mphCFCn8KxlvN9q/Vph+h7SE9hNgjRpUWGnayzqh kXysPdVWxDcWmSXfRww+MWb0usLDwsE7QwqF3akpH8uRJ7SKaAWnfLG3U/ohnbFKlGZU 5/Af+kkX/fTU47dSgS9Wrt3R6se1gFKjDJIhy9+zC/IX1YxAlxViCLss5hj/UKJKlxnq eq07tC+2+yWuaLPL/PhNiihte3KSwxyy8kRR0lfwBc3zN1BIawppZemDR7QtJxEW09rQ y79ryczJDvD6fj7KH4MG4jOHczIoGyd+iGKQlcULsLretVF23JQi1ZduObu2GZxM6m1s vCpQ== X-Gm-Message-State: AOJu0Yz0rEY5vwSMB1iuney4HysQCv43M74GEEgiK0BuTlHPQJTbG9Cf ZSwdoSxrYRT1nNGP4bqX7csvYqem5Eyi138u+YPD5tSwAgBXsHCsd60X1y3I X-Google-Smtp-Source: AGHT+IFBke+NY56F+94TYz1qiKCkMtmKgaq1IbH9TF/63VsxEkiQ9OhzoUZKmRWwD+0wTy/KVk2pwg== X-Received: by 2002:a5d:42d2:0:b0:37d:f4b:b6ab with SMTP id ffacd0b85a97d-37efcf93135mr2364724f8f.59.1729719116705; Wed, 23 Oct 2024 14:31:56 -0700 (PDT) Received: from localhost ([2a01:4b00:d036:ae00:21cd:def0:a01d:d2aa]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-37ee0b9bac3sm9765440f8f.94.2024.10.23.14.31.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Oct 2024 14:31:56 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Cc: Gavin Li , Bruce Richardson , David Marchand , Nithin Dabilpuram , Oleksandr Nahnybida , Robin Jarry , Stephen Hemminger , Sunil Kumar Kori , Viacheslav Ovsiienko , Zerun Fu Subject: please help backporting some patches to stable release 22.11.7 Date: Wed, 23 Oct 2024 22:31:52 +0100 Message-ID: <20241023213154.1231303-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.45.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 2024/10/30. You can find the a temporary work-in-progress branch of the coming 22.11.7 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 --- d16364e3bd Bruce Richardson common/idpf: fix AVX-512 pointer copy on 32-bit b34fe66ea8 Bruce Richardson net/iavf: delay VF reset command f665790a5d David Marchand drivers: remove redundant newline from logs e4a4087992 Gavin Li net/mlx5: set errno for ipool allocation failures 6c3de40af8 Nithin Dabilpuram common/cnxk: fix inline CTX write 6db358536f Oleksandr Nahnybida pcapng: fix handling of chained mbufs 6f96937dad Robin Jarry ethdev: fix race on ports in telemetry endpoints 4baf54ed9d Stephen Hemminger common/idpf: fix use after free in mailbox init 2d4505dc6d Sunil Kumar Kori common/cnxk: fix MAC address change with active VF b04b06f4cb Viacheslav Ovsiienko net/mlx5: fix flex item header length field translation 97e19f0762 Viacheslav Ovsiienko net/mlx5: fix non full word sample fields in flex item 2254813795 Zerun Fu net/nfp: notify flower firmware about PF speed