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 964F2A00C2 for ; Thu, 3 Nov 2022 10:40:45 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9219C40694; Thu, 3 Nov 2022 10:40:45 +0100 (CET) Received: from mail-wr1-f52.google.com (mail-wr1-f52.google.com [209.85.221.52]) by mails.dpdk.org (Postfix) with ESMTP id 7CCBE40693 for ; Thu, 3 Nov 2022 10:40:44 +0100 (CET) Received: by mail-wr1-f52.google.com with SMTP id bk15so1708307wrb.13 for ; Thu, 03 Nov 2022 02:40:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:reply-to:mime-version:message-id:date :subject:to:from:from:to:cc:subject:date:message-id:reply-to; bh=PapOh7NUaSbsOs6cUhb/mP05+mQJw+bCGggOpzTkS4E=; b=j3jAvcRsRS8vnfJT1oQboiYUH2Flcv4J1P/yKe+Eutn4QPdVzzQmigg198lBpcaVky HAJbfaMGKhTZYT3FRT+HIRrpqwPOfDj66VFMB9UsKMfj/IJzVudmmyyQCZWMrCEKOBmN 3hlmYkhVEbCIGuJsX50piaP/lo14ejDruMvnE7OgrF1IVwyfsSJA7+TnNAaZsFVzt8eH OJ6ABnMVSj+nvrL1K3DJZvpLgeaSDlqTrWXcUBW+2cmPWEcWvX09XO1q0hNVtEALliLe 6u6HEUsfkvqI6kAPrC8j2OBYsfcoPQMB5yIRPFcXKMxFCsRfDBU3b9VyCb45ocRRXxt1 5W7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:reply-to:mime-version:message-id:date :subject:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PapOh7NUaSbsOs6cUhb/mP05+mQJw+bCGggOpzTkS4E=; b=W3OkC7hrPuegLqTE4oahYVsozb6PtbbcRRCNPvb2aleMHYiRjRIEZNGubpLNb3VYTn vgHMY/2Is+VDa7VYiPcge7QpYDZpyA3AJXXEM6XEkmmjAl2b74LpccKhZKnC5Kvzxvco lsiURDUvqpgo0n0532Q1W3xYOxAqTSAyOSw51AXyUZBhFyltdjeMJ1l1ZpxirokhE9R4 cQ14oRJiiqax2FxI7NrBSM7nz0IHprEoZFyY6np2n+pjwKUVz6sxI4EDlWpn6l/o+3XG mjLamD3G5aSy4tEGRUoGTIan/coNx5HXkgwpO5hvavCxbWfTY+Ez/Hlu5/LhbjE9SF5+ 6AHg== X-Gm-Message-State: ACrzQf2zkjEhzSAQQwzKMEU2ZaItROW6l1ybT8AjCXS1Yv9ZcbVWp1NR 21IYMFul6OAEHiiHiResyDpEaHQV+CDw+ohr X-Google-Smtp-Source: AMsMyM7aZJc/h/46JDODPsrfFOkLcluM4xcBwG06PHeS/Iw5kkrlLF8iNMp9uAIFeGQUjUDTA5XhtA== X-Received: by 2002:adf:dc8a:0:b0:236:6372:551e with SMTP id r10-20020adfdc8a000000b002366372551emr17829392wrj.41.1667468443856; Thu, 03 Nov 2022 02:40:43 -0700 (PDT) Received: from localhost ([2a01:4b00:d307:1000:f1d3:eb5e:11f4:a7d9]) by smtp.gmail.com with ESMTPSA id f15-20020a5d50cf000000b0022e36c1113fsm381532wrt.13.2022.11.03.02.40.43 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Nov 2022 02:40:43 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Subject: please help backporting some patches to stable release 20.11.7 Date: Thu, 3 Nov 2022 09:40:37 +0000 Message-Id: <20221103094037.1103109-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 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 20.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 20.11 branch, or - Indicate that the patch should not be backported Please do either of the above by 11/10/22. You can find the a temporary work-in-progress branch of the coming 20.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 20.11] foo/bar: fix baz With git format-patch, this can be achieved by appending the parameter: --subject-prefix='PATCH 20.11' Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". FYI, branch 20.11 is located at tree: https://git.dpdk.org/dpdk-stable Thanks. Luca Boccassi --- 8ae946970e Abdullah Ömer Yamaç eal: fix thread name for high order lcores 09b5b2880d Benjamin Le Berre net/bnxt: fix error code during MTU change b38bd88beb Huisong Li net/hns3: fix clearing hardware MAC statistics 0d81da2559 Huisong Li net/hns3: fix RSS rule restore 8f81056e5a Qi Zhang net/ice/base: fix 100M speed capability 04ab2b2f0b Qi Zhang net/ice/base: fix comment of overloaded GCO bit 40ff47dd4b Qi Zhang net/ice/base: fix double VLAN in promiscuous mode b0472e210f Qi Zhang net/ice/base: fix input set of GTPoGRE 38ef9e1b99 Qi Zhang net/ice/base: fix null pointer dereference 27b7bdae1d Qi Zhang net/ice: fix DDP package init 3b8c645afa Zhichao Zeng net/iavf: fix outer checksum flags 1aaacea174 Zhichao Zeng net/iavf: fix processing VLAN TCI in SSE path