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 46A514568A for ; Wed, 24 Jul 2024 19:43:01 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 396D940B97; Wed, 24 Jul 2024 19:43:01 +0200 (CEST) Received: from mail-pf1-f178.google.com (mail-pf1-f178.google.com [209.85.210.178]) by mails.dpdk.org (Postfix) with ESMTP id 251904026F for ; Wed, 24 Jul 2024 19:43:00 +0200 (CEST) Received: by mail-pf1-f178.google.com with SMTP id d2e1a72fcca58-70d316f0060so828166b3a.1 for ; Wed, 24 Jul 2024 10:42:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1721842979; x=1722447779; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=FIKTMh+DJwTO4s79S9D4Kuoim6Nl2EoeujMtPkIMpF4=; b=j/GOObiGPqhwMxgdzkoZ1wEmC/F+LU5URx3wvzVVMxCO8HX2kfATKF3fWAf4QRhbE5 5j5mi6C3ZGheoJLGwuFebbjK5X28uGN8LBQZfNYGELFJSUQbrAl4286pXYCN9Mr8oe/U ZXNvHAiQQmHQk0a2l7qYdZYWR3Y6uIg0LkI8AGgZ2VcDS0pFEcQyR/gHG0iZfTDqmmG+ SjN7cyXW90+Cad6Q2Np4cQ0tJXr0hVva70lPGorhbI3LYEplKMdo0C4Lax0Bt4zqoY7V rfpqEgw6JBLdR4Xvxqu5OkII00oNY06T/cLPK6y+W+dfRnXmTSmskD2Zq/sjnv4B+KCE DEqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721842979; x=1722447779; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=FIKTMh+DJwTO4s79S9D4Kuoim6Nl2EoeujMtPkIMpF4=; b=CHFLgMfRlkzVlkU33ciofzdxgzXIfNg2tiy2gr3Uz1+8Mmng7dIVwaq9CqdM6u9x4u kj0Ujcn46GDBrZUbIb4b8qjNndTRTAPj/oXApm9O8LXNwXrrzMG3VjYNCC9Ef5xySy+u beI5sGmCL7/gITFYfMsPueWA4UBRon1UGgAqnlsEBUK7k+xkxbkZK2rfIxwY0SNEahk0 spFsqAqaK/qLXoocUyDrMkreIW0L8qEsJzCqwFEL4qdBVSn/RTDa8AOPl9hW7pVL05jH /30fMF2ajJAZkMZAoD9I/9EN5sq8UZKm4TjNDHEjZB+j64k1ynvkQw5TTuG4aWJ6lulm Hzjg== X-Gm-Message-State: AOJu0Yyy2JWy7Ejq5Y/h+RU9m5aNUCD3LLos43/tSzzjvSvkldW41S1m yJqj3NQglBhJZMvp8H0VJTZC8hbWt2g55g7B/OL248l83NxcSpixQWjGNJSVvic= X-Google-Smtp-Source: AGHT+IF4HxB2YbB7rIE7OHSsrC1OjiJEGg94PzOLk7XFRbYAeZRJH8+6xUNZihC98LZCHisM1HSCMw== X-Received: by 2002:a05:6a20:a12c:b0:1c0:f630:97a5 with SMTP id adf61e73a8af0-1c473eaa212mr648243637.10.1721842979022; Wed, 24 Jul 2024 10:42:59 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-70d241803fdsm5653760b3a.220.2024.07.24.10.42.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 24 Jul 2024 10:42:58 -0700 (PDT) Date: Wed, 24 Jul 2024 10:42:55 -0700 From: Stephen Hemminger To: luca.boccassi@gmail.com Cc: dpdk stable , David Hunt , Tadhg Kearney Subject: Re: please help backporting some patches to stable release 22.11.6 Message-ID: <20240724104255.28ba1adb@hermes.local> In-Reply-To: <20240724113614.617441-1-luca.boccassi@gmail.com> References: <20240724113614.617441-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: , Errors-To: stable-bounces@dpdk.org On Wed, 24 Jul 2024 12:36:14 +0100 luca.boccassi@gmail.com wrote: > 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/31/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 > > --- > 93db1cfcc3 Stephen Hemminger power: fix number of uncore frequencies The #define for RTE_MAX_UNCORE_FREQS was introduced in 23.07 by this commit so backporting directly doesn't make sense, maybe an alternative fix. Author: Sivaprasad Tummala Date: Wed Aug 16 03:09:57 2023 -0700 power: refactor uncore power management API Currently the uncore power management implementation is vendor specific. Added new vendor agnostic uncore power interface similar to rte_power and rename specific implementations ("rte_power_intel_uncore") to "power_intel_uncore" along with functions. Signed-off-by: Sivaprasad Tummala