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 9C060A00C4 for ; Fri, 18 Nov 2022 00:16:58 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 70C924067B; Fri, 18 Nov 2022 00:16:58 +0100 (CET) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by mails.dpdk.org (Postfix) with ESMTP id 3AA164021F for ; Fri, 18 Nov 2022 00:16:57 +0100 (CET) Received: by mail-wr1-f49.google.com with SMTP id a14so6426795wru.5 for ; Thu, 17 Nov 2022 15:16:57 -0800 (PST) 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:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=FYT+wiyM5rIJSeZkKKCJX9KddjZZkRxPHQj9uRtQoDI=; b=LHhCGf1/s8ntx7vBqBlu3pImwTsWmflmnHskfHctMaYTvUTdFmHc0z8bKNxndeOO/+ +2OBo45536+slza6+rrzy0u3rf6eRt/YHIuzHm0M6rYkDmB78HnDa6m52U0LUyxbbJ6w /bWeBW84X3de/XfkmSiSb0azb9ZtGxAxydoeHfD41ALA3c9fbz6MSIYf+zkLgRjrafEz FdDEUi7WnoJDll+FbO2pIn9d+s9xrR1AiDimSpiSRVg7SWRIBJUKditM3l3peZfIpQa2 3fvbu90Mg/1ieXRnYHMVINFFR3JKe0BQ7/F0d5aK+qMfMuldynrAD4MvMKDK5HZi+o2T ikCA== 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:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=FYT+wiyM5rIJSeZkKKCJX9KddjZZkRxPHQj9uRtQoDI=; b=ATOS/2Kfq2IUYCLbLtYpt0qvGXsViOY38kO7MWEHIgHTlkwobpO6IIH0lmbWRXAGS1 Z/wxIkZK9RnFW1dy0680vF764pgKSPTcAmQNwc1a6SzYCgFjp0CErS06DNpB3JBDPIt8 prdP7OgacVKcKD1jo1+NtJRQE91QhfXxbyU4FHgQaWA7T5bGmTREzCnKDZN/GIctrpUW FM2WjKsxB8QNaX2pDtFrG+Jqa3irdiLXMv+gvJ9go6382J4vhCH/cRbS5LOnYG/Y3DSZ B/JfAy8Adic7bveByoStbUzJkAnoC1gpiA96O0+0zpGX/gOfJO1YyW9O8m6uGIBNAlNJ 25LQ== X-Gm-Message-State: ANoB5pmRJXvzQjHjppLGV/dqOTYZn5gL95xh4AfSgOWwFgwFc/6RN5fL 1pID42jE36AZBFYRvajV7YcHW8NHcgduJg== X-Google-Smtp-Source: AA0mqf5rCEXZruc65b4M75v4PK53jM7oyvjyxk1hCM+VtmxBw96iokpnHky5GWTc0M7DckfRuCXZzg== X-Received: by 2002:a5d:4b86:0:b0:236:5702:50b1 with SMTP id b6-20020a5d4b86000000b00236570250b1mr2746574wrt.26.1668727016615; Thu, 17 Nov 2022 15:16:56 -0800 (PST) Received: from localhost ([2a01:4b00:d307:1000:f1d3:eb5e:11f4:a7d9]) by smtp.gmail.com with ESMTPSA id w17-20020adfcd11000000b0022e653f5abbsm2127089wrm.69.2022.11.17.15.16.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 17 Nov 2022 15:16:55 -0800 (PST) From: luca.boccassi@gmail.com To: dpdk stable Cc: Dekel Peled , Frank Du , Hernan Vargas , Jiawei Wang , Jingjing Wu , Liu Tianjiao , Matan Azrad , Maxime Coquelin , Nicolas Chautru , Qiming Yang , Qi Zhang , Shahaf Shuler , Shun Hao , Viacheslav Ovsiienko , Wenzhuo Lu Subject: please help backporting some patches to stable release 20.11.7 Date: Thu, 17 Nov 2022 23:16:53 +0000 Message-Id: <20221117231653.613024-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.34.1 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 2022/11/24. You can find the a temporary work-in-progress branch of the coming 20.11.7 release at: https://github.com/kevintraynor/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 --- 63bd264485 Frank Du net/ice: fix interrupt handler unregister beaf1f876c Hernan Vargas baseband/acc: fix double MSI interrupt in TB mode 3e13a6ae95 Jiawei Wang net/mlx5: fix mirror flow validation with ASO action e9de8f33ca Jiawei Wang net/mlx5: fix source port checking in sample flow rule afb98009a0 Shun Hao net/mlx5: fix assert when creating meter policy