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 01B2AA0543 for ; Sat, 5 Nov 2022 18:26:07 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0837740151; Sat, 5 Nov 2022 18:26:07 +0100 (CET) Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com [209.85.221.44]) by mails.dpdk.org (Postfix) with ESMTP id 118B3400D5 for ; Sat, 5 Nov 2022 18:26:05 +0100 (CET) Received: by mail-wr1-f44.google.com with SMTP id l14so10935244wrw.2 for ; Sat, 05 Nov 2022 10:26:05 -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=9nL0SkhKMwXr0I3OKLfo/CaUCIvJcuvOw4k2TWl0hQg=; b=ZfCSUxGyf7Rk9zzDzDr+n8jYB5G1tdYMD7UqKHmfHv9YGYCRL0n5tHp5qEDwr/vMic re1iOYDeku5u4kIqvwkrBTl70Oupjtx5zg3OGtaRUDID3UZucCxCgmzcbhmeEVLwThMz EoDnN++lTkPGBA0GYA0CWG4hbYvZ3+3BQbcAqpsqDm+tQlz5DvlVGDdcE2Tm0AZrJpWx oWEQeHH+xbpzuS2cX2y/kolNiHAPnpzx5Zxj+p+N5JXY4o+XCYeEE79j37Y70Lv7KfLn zAL/5RMwFU7kehthegfYzZHuEqlIHjrKLN4Qnh0/bFhJzc+12/jh0vj4PsPfj3hfIANz IkLw== 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=9nL0SkhKMwXr0I3OKLfo/CaUCIvJcuvOw4k2TWl0hQg=; b=i/BxZV6+w/Tix+8qeGRuzdUwfreuQ2kYOtv6OQboeoT0B6xi7t3RyMTL/8lgiH1Exf IcRyWrcSRRc+y+cEoRSvwv2F9D7avsBhRBk+d+FbZRDuQht8R7UAxMOLtZFxzf1gw2x3 6WgdgNSStkwk4otnA66I6zPzODTgQsOMH1hgzeQUqxfmH7eGa+fEHT9Gp8gMnU5kplnM mBQ21zs+MA05fHrrAYhCIRrqiU8NXkIQ1O6c2pYAGb+/pznDC/8zmGlHkNMYibG1OELU oyQ/h++PDP6Ipa27H79UXJ3h5DbZfoWh1S8q6/L7PAcAtCyzPdBVwGUUFJ2AZUR+Aa2w UeZQ== X-Gm-Message-State: ACrzQf2ZC8+Z3S1y5PdNwXB5FJ7W8FuIZMvLRbRiK/+qkf+KfxEzVQ4u RFxh7NRGl6IerenKvT9wMdDetVcj4CcSSA== X-Google-Smtp-Source: AMsMyM5wBEOKWCfkBkC/g2+JxoFDqtGd6zzaa72TukInbAYxq1cLjt5U1VkuzfGIXLh3cXDWve3Xxg== X-Received: by 2002:adf:d213:0:b0:236:9cb4:20a9 with SMTP id j19-20020adfd213000000b002369cb420a9mr26409588wrh.581.1667669164382; Sat, 05 Nov 2022 10:26:04 -0700 (PDT) Received: from localhost ([2a01:4b00:d307:1000:f1d3:eb5e:11f4:a7d9]) by smtp.gmail.com with ESMTPSA id l22-20020a05600c089600b003c6bbe910fdsm7434841wmp.9.2022.11.05.10.26.03 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 05 Nov 2022 10:26:03 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Subject: please help backporting some patches to stable release 20.11.7 Date: Sat, 5 Nov 2022 17:26:01 +0000 Message-Id: <20221105172601.1522548-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/12/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 --- 2df5fe2023 Hernan Vargas baseband/acc100: check AQ availability 5802f36dd4 Hernan Vargas baseband/acc100: enforce additional check on FCW 75114f78cf Hernan Vargas baseband/acc100: fix null HARQ input case c24d53b4cc Hernan Vargas baseband/acc100: fix ring availability calculation 459531c958 Morten Brørup mempool: fix cache flushing algorithm 927cb43fe9 Pavan Nikhilesh examples/l3fwd: fix port group mask with AltiVec dbad6f64f9 Peng Zhang net/nfp: fix internal buffer size and MTU check