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 DA37042DA6 for ; Sat, 15 Jul 2023 00:51:20 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C45B140EDC; Sat, 15 Jul 2023 00:51:20 +0200 (CEST) Received: from mail-wm1-f52.google.com (mail-wm1-f52.google.com [209.85.128.52]) by mails.dpdk.org (Postfix) with ESMTP id 3687B40DFB for ; Sat, 15 Jul 2023 00:51:19 +0200 (CEST) Received: by mail-wm1-f52.google.com with SMTP id 5b1f17b1804b1-3fbc244d384so22818385e9.0 for ; Fri, 14 Jul 2023 15:51:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689375078; x=1691967078; 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=s8R3c86gnisjRiugDxJWroyhIHK+bXlJmOu5Kjy0bMg=; b=CQ1aXpdm8+c+YPtkI4TdSg+q89RKTjuqF9BBjUgJK9ToTXTbVUPfpR5w6sBqGfwnS4 fr2yhZH7wIWv0v533JxZ2N+pz7stKUz7t5awcgOKKrK0wumFk2skBK3OiVO/fjXvsuIn K0MDdLv75kZvxPtAh/ZiZRRwkzghFo6NMVM7k8ptuSyITdTRk+8khZNP9dWdwDZHmnj6 cPs9ZDw0Tf5TH2Qbd55JUzhxrMF/enQN1xxx7N9f24o/A6vGuyxxA+0QCPJR2dWXxqM2 uE3c+/11Xkkq/Zb02ZPgcEJ4h5ZgPtbuPSFCbBzrNLz7EDk7AY3ZZy8PjDsUC65FJk4u xidQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689375078; x=1691967078; 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=s8R3c86gnisjRiugDxJWroyhIHK+bXlJmOu5Kjy0bMg=; b=eUyTNxibxUqmWhKjKEWq67Rq/N8+LESCmWQKx05Ij/WC96pT0FxURvaZUlp2lYTh89 uXQeZMAOv9mTRxJCt+qR9ergiPoikVZhnxZXk9Tem8/F6xBo44yugvp3CEXKM0eVqeLj YsI5q7ppwX75LdQCKtfWR1zBc0qpcQr9+BMxhd0G/jvARVxiyy3Onl+4RAyVvxYqTWiL racVUaoxJQBun7Y+WxOL6Wh/ahbwQPJBFWzpgJsZlIX6tbDWpwDSe/0JZGyCk0MFGXO1 bSSPCVorBXlPxSTQsQqI9yelDlgV78jPkDQDAZBJOOmqjRKR+XirNEr1d3j7iY9VtEuy AOtA== X-Gm-Message-State: ABy/qLYjlHpXqG3MGJICr/k6Nb6cYWjWOV1x6abTxr4rlh4cpuNyQLYC xYIojQSgg7Dxi4BvDONaWA5vAX7/Nh9ZLS2qljY= X-Google-Smtp-Source: APBJJlEjV7PJ/hXFHMeoBv1eMQmMZYYe2j9boJhWN3j5MgRs9yA6sIBUyST6SPc5kvhy1MOdHfK8cg== X-Received: by 2002:a5d:4ccc:0:b0:313:e6fa:fae4 with SMTP id c12-20020a5d4ccc000000b00313e6fafae4mr4904054wrt.38.1689375078530; Fri, 14 Jul 2023 15:51:18 -0700 (PDT) Received: from localhost ([2a01:4b00:d307:1000:f1d3:eb5e:11f4:a7d9]) by smtp.gmail.com with ESMTPSA id e19-20020a5d5953000000b00315af025098sm8212715wri.46.2023.07.14.15.51.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 14 Jul 2023 15:51:18 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Cc: Ali Alnubani , Anatoly Burakov , Arkadiusz Kusztal , Ashish Gupta , Beilei Xing , Bernard Iremonger , Bruce Richardson , Ciara Power , Deepak Kumar Jain , Ferruh Yigit , Ferruh Yigit , Fiona Trahe , Jian Wang , Jiawen Wu , Jie Hai , John Griffin , Song Jiale , Vikash Poddar , Wenzhuo Lu Subject: please help backporting some patches to stable release 20.11.9 Date: Fri, 14 Jul 2023 23:51:11 +0100 Message-Id: <20230714225111.1095683-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 2023/07/21. You can find the a temporary work-in-progress branch of the coming 20.11.9 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 --- 8b4618a7b4 Ciara Power crypto/qat: fix null algorithm digest placement d7d802daf8 Ferruh Yigit app/testpmd: revert primary process polling all queues fix 5e170dd8b6 Jiawen Wu net/txgbe: fix blocking system events 7cb939f648 Vikash Poddar common/qat: detach crypto from compress build