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 9A16442814 for ; Wed, 29 Mar 2023 03:05:54 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9400140F18; Wed, 29 Mar 2023 03:05:54 +0200 (CEST) Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by mails.dpdk.org (Postfix) with ESMTP id 1796640EE7 for ; Wed, 29 Mar 2023 03:05:54 +0200 (CEST) Received: by mail-wr1-f51.google.com with SMTP id m2so14013097wrh.6 for ; Tue, 28 Mar 2023 18:05:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680051953; x=1682643953; 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=kICL6I89OrUesmsCjy1yoBxeybr0QsofzGyFn6XoULA=; b=LBZSELlHj91gKFeTexPvXfMzNUSvhAvVlgZYXmrCOXt1JChWPDXOa35HF/fPjK8z16 VyzDOXePIvQdBTmFXOum+rXkPmstvNQV5fnVm9/9lSX4u3mNV6TzsufOv9pVNlhUJxoz Zl0lBe8RAOetMEfh6613FQ4vIPQIBa3qisXeYAb3q6x4GZ9Qy/OyRrNNe5d6CBFYOcHO N0d41R9GEbR4BZyyRUiC6ZQ18l/T9gMtFM5QA/C0wXHjS0WNPBqd5V42f4qyzBXczvtk kpItXa7ZIbCmmq86FsmVjsvUcFddzqOdBy9cRJUcG8shu65ke3kwyf/aw+MEH73TPQHY KR/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680051953; x=1682643953; 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=kICL6I89OrUesmsCjy1yoBxeybr0QsofzGyFn6XoULA=; b=iyfBiqFYcr+hJAKY71IHXeT4317RxZUJTQawjXGfpF9qQ3IDfMbLTjFwHR0WjQguBd 5dzpBUGxsFiA0IyezU50n0J1JGs+oJzSIjBFgoaDSHSq5v6n38JVGUlbav0fa9kA8Ced +EcK1VWVHYj84Mv9bQWcFUNpmJCDxRefluk/Psp26ytN0UBpvt7ossdvpsWju2Kw0jpl cbltTMvlQ/IASEGWYaY+2XWe/mRpxEEJAwfT/82O7KyU9VlI6cztoiBpb46Lg4cclDln /dDsA3z+TQUMr4wUiT+q5CAA70ZftvQrxZbuOAzu86aEFFR5JuEMjGYA4n4DGv/XlKzG g6XA== X-Gm-Message-State: AAQBX9fVKdw1NWbreOCn8VW9UlCpbmDWedXM56RjOUU3LjQq3y5NLUmr VL/Xgx18ZHqH4/uU++7Gfp/XN40axrE= X-Google-Smtp-Source: AKy350bkvTpEN2RtxK62kwiCM1c9VL6hSVjFUrEsgMCOm4EJ9PS8dgs1OwU2qK50v7sIzXFzTTAiYw== X-Received: by 2002:adf:fa8b:0:b0:2d8:36de:bb79 with SMTP id h11-20020adffa8b000000b002d836debb79mr13662252wrr.9.1680051953426; Tue, 28 Mar 2023 18:05:53 -0700 (PDT) Received: from localhost ([137.220.119.58]) by smtp.gmail.com with ESMTPSA id s2-20020a5d5102000000b002c71b4d476asm28719268wrt.106.2023.03.28.18.05.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Mar 2023 18:05:52 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Cc: Beilei Xing , Bernard Iremonger , Ferruh Yigit , Michael Baum , Ori Kam , Wenzhuo Lu Subject: please help backporting some patches to stable release 20.11.8 Date: Wed, 29 Mar 2023 02:05:48 +0100 Message-Id: <20230329010548.564029-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 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 31/03/23. You can find the a temporary work-in-progress branch of the coming 20.11.8 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 --- 7bdf7a13ae Michael Baum app/testpmd: fix encap/decap size calculation