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 EA35343D6E for ; Thu, 28 Mar 2024 18:28:05 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8F26E410EA; Thu, 28 Mar 2024 18:28:05 +0100 (CET) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) by mails.dpdk.org (Postfix) with ESMTP id 38EA7406BC for ; Thu, 28 Mar 2024 18:28:04 +0100 (CET) Received: by mail-wr1-f41.google.com with SMTP id ffacd0b85a97d-33fd8a2a407so808056f8f.2 for ; Thu, 28 Mar 2024 10:28:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711646883; x=1712251683; darn=dpdk.org; 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=YhW+SmCmhWZJAbDavBf2NfItWykMaobeAvKAhecPTHM=; b=c3nSHe0CzkpOlMGmmvbPmXC9lzwHl+gzA47Ms8HYJNvln6kLnqNQTKzeII2w/r5J9/ aJD2H5k6hnVN96upQyL/Z1QX29VGzRpQo/30hOc0/jPp1DLcwHXpMz/1Fb9AcWatseDH bL5rJBpfbd8M+JY9T4dSCR77uaY9rR2opROXtBP5+rzdaOtprkxIPBnagRAdPB/tT68N spWAGUZrEQTxb67nONuX8JwDMXWrhLb5KC2NnHW4M7no36xFSuQfvf7EXT19r4LDjf8W y3GeCAL/kO1XDORT/a4I/n87xNaSBUtKBcXFlU2PZmYetBn742gvr3zlsiTu9JnzXk8t f0OA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711646883; x=1712251683; 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=YhW+SmCmhWZJAbDavBf2NfItWykMaobeAvKAhecPTHM=; b=LRtOc/4g9k7qYoAAvfXsOAEyB/X3bnisAwyOAbKKSnre43hs2gNlXOtbpQawMFv+hx UL6c2ImqBZkEmgFuJ6rN/uGnVODRWWH8IlmTUymjMy272/xvjNs1t59/fr9ofQUvLboz dCEnr0Hcj1STBznLqY7aC3BFjHHrnIzcYn3ZoXeq4IA29rlhDTXCuQ3Rw92eUq/dua6J h2qIFDhSkOjj6zPYxTugnQeZ9qdz4764eej2yWBsVQD5omM0Ju6AQoU1sXxaXZWG0u3I nMlzcmpY/nx6ZC+NgGlkUh+8/UrQtHw7yYSO+nz9sbj5TObTZhTxQuiAuwxDlPTvNbxO sFvA== X-Gm-Message-State: AOJu0Yzpqh3K8StnGaxS+YZN+rfH4Td5FZnq3Hx6LaF+vb4AooRozMo/ x6kku38lbWKITbmNFpS5/mGdmvi7uQJobKSjieVlvwta+oszKflA1eOhT3SrPO8= X-Google-Smtp-Source: AGHT+IH3t7D2blNCGC7ClWc4v228u7mvIp5YsBNK2XzwRtd48m0uT9xvHfMxyL5QZNoltZUhEPd4Yw== X-Received: by 2002:a5d:4dc8:0:b0:33e:d470:da8f with SMTP id f8-20020a5d4dc8000000b0033ed470da8fmr2690818wru.17.1711646883326; Thu, 28 Mar 2024 10:28:03 -0700 (PDT) Received: from localhost ([2a01:4b00:d036:ae00:7aef:1aaa:3dff:d546]) by smtp.gmail.com with ESMTPSA id t1-20020adfe441000000b0033e756ed840sm2248593wrm.47.2024.03.28.10.28.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Mar 2024 10:28:02 -0700 (PDT) From: luca.boccassi@gmail.com To: dpdk stable Cc: Thomas Monjalon , Nithin Dabilpuram , Itamar Gozlan , Stephen Hemminger , Kumara Parameshwaran , Honnappa Nagarahalli , Gregory Etelson , Dariusz Sosnowski Subject: please help backporting some patches to stable release 22.11.5 Date: Thu, 28 Mar 2024 17:27:45 +0000 Message-Id: <20240328172745.3879385-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 22.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 22.11 branch, or - Indicate that the patch should not be backported Please do either of the above by 2024/04/03. You can find the a temporary work-in-progress branch of the coming 22.11.5 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 22.11] foo/bar: fix baz With git format-patch, this can be achieved by appending the parameter: --subject-prefix='PATCH 22.11' Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". FYI, branch 22.11 is located at tree: https://git.dpdk.org/dpdk-stable Thanks. Luca Boccassi --- df33fb53e4 Honnappa Nagarahalli rcu: fix acked token in debug log 063cddfc74 Honnappa Nagarahalli rcu: use atomic operation on acked token 547f294357 Kumara Parameshwaran gro: fix reordering of packets 323b626a86 Stephen Hemminger net/sfc: fix compile-time check e23edbc509 Itamar Gozlan net/mlx5/hws: skip item when inserting rules by index 3232c95d2c Nithin Dabilpuram net/cnxk: fix indirect mbuf handling in Tx 5ecc8df4fa Dariusz Sosnowski net/mlx5: fix async flow create error handling ff9433b578 Dariusz Sosnowski net/mlx5: fix flow configure validation 727283742a Dariusz Sosnowski net/mlx5: fix rollback on failed flow configure 4359d9d1f7 Gregory Etelson net/mlx5: fix sync meter processing in HWS dc7faa1351 Gregory Etelson net/mlx5: fix sync flow meter action