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 D8E18433F5 for ; Wed, 29 Nov 2023 03:33:42 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D257B402CE; Wed, 29 Nov 2023 03:33:42 +0100 (CET) Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) by mails.dpdk.org (Postfix) with ESMTP id CA2A9402A9 for ; Wed, 29 Nov 2023 03:33:41 +0100 (CET) Received: by mail-wm1-f41.google.com with SMTP id 5b1f17b1804b1-40b472f98a3so21884965e9.3 for ; Tue, 28 Nov 2023 18:33:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701225221; x=1701830021; 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=ZyivkaKqm9cnpPYAwJnYpXSNdONaH6s8eXIBDNOCTiw=; b=J4OjbAP7n+P3aTIJ5rD9tH0OR23H4+866YLZw0oslrWKNJaMlC6j5b9SL3LA4zLb7o SE7tlg64f52qftJPUHjUaE+/8y7meKhgx5OWjPW0mJ/sN7IFw1NIYWlEtOQMziBsJsS8 UPYW9Z/fUvYtAvCEQACT7BYaeoYyN2Ok39PLekm5TVXsvPzDcScg+m8UF/NejrVFvERb laC4RaZn+iE/AXlG1YJEk26wBZw4wMFlqpkTu8d48jopa10bSjoPeAbzS/PQxVk/i6qz ZpzQ6AGBjtEXdwhZoGAzqv6nmeizl83zb6HfDlVMffnJVKB/T6nDCAOYvWuT+QkiklMy Xy0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701225221; x=1701830021; 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=ZyivkaKqm9cnpPYAwJnYpXSNdONaH6s8eXIBDNOCTiw=; b=MvBVDRpgrs3vwrWQC60IhbQfAkRgEFzcoZQhDe/hDKeZ1F759q34FU8aY8S5q/jFv8 SetMYMGlhWY0U9fsiTi5zIxtTv6DN0HEyz0hCUOwkTDznEDgfTQYpYBcOz1TqrRuph3h EUAPwxuov0j3LwS+VBlqoY29XulO4l95L1GSmWnLsEBdJhDW+zsJpaq2AYrsOx21yd9H xF9YYU6roUUI9sPCfKGQ7JvNsjM+LM4hHRKdRbyyRs+a1bG8vvj4Y07SMoGuFFHy+Q9f 07FyyHqdmhH6weVdn4DmbwE4PjhNABHukDHamcowD84q0JfJbhFXrcsL2MlY/AsF6/8z /1IA== X-Gm-Message-State: AOJu0YzI2mAoZI2bug3gl5QVROPlq1YjQPG6MYXr2f0fGyBuEBnkcRBI bCPIaWFk1JkfQajgIOTP80nTas2e8B5q8g== X-Google-Smtp-Source: AGHT+IF61OFkQAobuaw1Nz3a9evide95cZd12Eu1ZfIX/7l1Ku32Cv6hgLZYynQIV0DPG/0IGR65Qg== X-Received: by 2002:a05:600c:4ec7:b0:40b:4b93:a369 with SMTP id g7-20020a05600c4ec700b0040b4b93a369mr2786462wmq.14.1701225221200; Tue, 28 Nov 2023 18:33:41 -0800 (PST) Received: from localhost ([137.220.119.58]) by smtp.gmail.com with ESMTPSA id t17-20020a05600c451100b00407460234f9sm362508wmo.21.2023.11.28.18.33.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Nov 2023 18:33:40 -0800 (PST) From: luca.boccassi@gmail.com To: dpdk stable Cc: Chengchang Tang , Dengdui Huang , Hao Chen , Huisong Li , Jie Hai , Lijun Ou , "Min Hu (Connor)" , "Wei Hu (Xavier)" , Yisen Zhuang Subject: please help backporting some patches to stable release 20.11.10 Date: Wed, 29 Nov 2023 02:33:33 +0000 Message-Id: <20231129023333.1781101-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/12/01. You can find the a temporary work-in-progress branch of the coming 20.11.10 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 --- 4c40006c4b Dengdui Huang net/hns3: fix ignored reset event b59a0cbec8 Dengdui Huang net/hns3: fix reset event status 94cf4db160 Dengdui Huang net/hns3: fix VF reset handler interruption