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 DD06A455AD for ; Mon, 15 Jul 2024 17:33:13 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ABC6040DF8; Mon, 15 Jul 2024 17:33:13 +0200 (CEST) Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) by mails.dpdk.org (Postfix) with ESMTP id DF4C140A71 for ; Mon, 15 Jul 2024 17:33:11 +0200 (CEST) Received: by mail-lf1-f48.google.com with SMTP id 2adb3069b0e04-52e9944764fso5115891e87.3 for ; Mon, 15 Jul 2024 08:33:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721057591; x=1721662391; 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=zJ4A8oRkOWuCByuTfoKXB5nYuwXI69MpSeJJPtPh8e8=; b=gB0kTYWG4YOI3Lt9YAbFdZB6/eWlcZ6FsFzR490aevf839+GtEAzK0Y2jNqYfkB51+ WOUGUF1iix8FNua3Qg+jg2ElxdzU7QyXELy1b4aYUhWFy0dKngUhCS/NEAxffU6MOyEk RBBplDZtggG3rNy/jZx896gLWgwrOXQObDWpwK4DoJyZgVI2vpb4D9zJ6TM6j1hgqduU lMqPC6gXXiAMtBI7tI/WE3MnXh3AFy9hIhLJao1HXs2X072lIs2IXIry32lmWpjbeMZ8 n5z6CmUjGnNwCEOJsYrWFa0tAvyTq+It20zktyh4SxSsblmsiQgLIo5oOCGrEj1ThLRd rvSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721057591; x=1721662391; 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=zJ4A8oRkOWuCByuTfoKXB5nYuwXI69MpSeJJPtPh8e8=; b=AtKno3rxoFPwc48fzI6MIC+Sf3jtgFDynwM5QlbiPXXc2Vngereb4ErMexmdpYsFYQ aRAH4cZglwhnX7kyuN5meQtMoHjrnik4WR3/j2EIXElvYnwVWrjl3SOgBkx5bh5vQUOC 04u9ZK5mvSXk4UediIXA3QbH3gqT+6urAr1WdFV/BfqoKKcfyOF/l0q5OlYVUQ+CZs9G Ng4pegMFrl/2PcGsLjio0SpvK+UgYMfhYnV0vrGwMEsbPd2vZzUpu0eLe8HE6gok9wgd NbQJPsy5Zs4TCsjzzJL/mWVyksW0BvOzUPFND4VDyrH6GFpSwiqzeEw9UmPxRRK5yek3 Ubvg== X-Gm-Message-State: AOJu0YzUDDYkqwLogPh+QvhWzojxaUqJ3YF6ixMRhVlfmo1ifjdKhYT4 agBAa8GOXO+7VYbbesCsMJ9ebnVNOgETlvbi0XOIcohQhB4SEO25vSDDnJNBCs4= X-Google-Smtp-Source: AGHT+IFP3ttpDts9gYezjOTncBe+qht0ZzQzLoNTMLB8s5jM9nWJlWDA8AUQzGt7BGfCGBbRNxOK+g== X-Received: by 2002:a05:6512:690:b0:52c:8aa6:4e9c with SMTP id 2adb3069b0e04-52eb99d28bamr14010060e87.65.1721057590814; Mon, 15 Jul 2024 08:33:10 -0700 (PDT) Received: from localhost ([137.220.120.171]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-427a5e8387fsm91546105e9.20.2024.07.15.08.33.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Jul 2024 08:33:10 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Cc: Bruce Richardson , Chaoyong He , Ciara Loftus , Ferruh Yigit , Frank Du , Ian Stokes , Jacob Keller , Kevin Laatz , Kiran Kumar K , Long Wu , =?UTF-8?q?Morten=20Br=C3=B8rup?= , =?UTF-8?q?Niklas=20S=C3=B6derlund?= , Nithin Dabilpuram , Paul M Stillwell Jr , Peng Zhang , Qiming Yang , Qi Zhang , Rahul Bhansali , Ray Kinsella , Satha Rao , Satheesh Paul , Sunil Kumar Kori , Xiaolong Ye Subject: please help backporting some patches to stable release 22.11.6 Date: Mon, 15 Jul 2024 16:32:59 +0100 Message-Id: <20240715153259.2231242-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 07/22/24. You can find the a temporary work-in-progress branch of the coming 22.11.6 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 --- 97039941b2 Frank Du net/af_xdp: parse UMEM map info from mempool ab1bb0c402 Peng Zhang net/nfp: add check for numbers of VF representor port fde2a1cb34 Rahul Bhansali net/cnxk: postpone disabling NPC Rx and MCAM