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 7A96F43337 for ; Wed, 15 Nov 2023 12:47:02 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7225540294; Wed, 15 Nov 2023 12:47:02 +0100 (CET) Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com [209.85.128.47]) by mails.dpdk.org (Postfix) with ESMTP id F366D40285 for ; Wed, 15 Nov 2023 12:47:00 +0100 (CET) Received: by mail-wm1-f47.google.com with SMTP id 5b1f17b1804b1-4084e49a5e5so57403175e9.3 for ; Wed, 15 Nov 2023 03:47:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700048820; x=1700653620; 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=Ei01ysfGiENgbbhxf2Qh1k6ZmY7KGfWNmWN9W9xRBnE=; b=OfD7467gfcG1G2hse/otfqCXBB+nQwNmuBnJ1QPut7kEPNSB9nzuEyr7mEcdPiPt4F rbGPZ4/KY9wMZ3gnn8gnnjTxmhPhq5+77wjvWaggX2UefO8nKzi0bB0ihzyYYvwhKixG khWW8ooz6CbhLM5Tz48qh5hsxI7IqALMNo1zwAvKo4hJ5KZmySHPxthFonKevAfJi0g9 WKFlZ1iOzmekDdFIyNY3K+jS9Gb4zL0JjxP0hyYqmDXFCUKPXK0K3NGMRYXwoFHADp84 49kS2yWaIQxnwu5FC7/hlmI6n57EIO+sX6VcsMUXKWDYdZMk5id00rysckVC1K8shNHG GRmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700048820; x=1700653620; 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=Ei01ysfGiENgbbhxf2Qh1k6ZmY7KGfWNmWN9W9xRBnE=; b=hCsynO7wZPkhGugsCIDsXZM+iy/pnFsVsCJt6NXh+yifjozPh9qgIiaj4l13trSjqC 4I8/2c3WlhAv41FvVpQ57WPIQkrwRBIPtEp58BYbNiv/8VCywWN9I7O6jqsc1frFNFwC L1gZmWP+fd8XkZKhDJNTFm3pcIQNyljoZnYKTkwXkCthoD9tjt0pFAzSh4pZsgSJLDu7 ++fYqOktvwbGruglVxB+xXIhs9mdrkgCHQX6KFlXLdVTAowwFiuQkaPkUBtLKzFf/c1u x6N7HBGJlLnav95rp7+VpjIBaMmoIT1vmug3ud/5JkhrQcYZ/VM3AsXk8jsCAiJ4WiFO r1aA== X-Gm-Message-State: AOJu0YzacRFRERYlqpN7mBpBcxB1GvoosrNUx3f301z3BRgUTXeyZnmF hNZRDc53yQVrtp1WZ2GaRVtY30TpAR5dC7IE X-Google-Smtp-Source: AGHT+IGQ9f6gTeQA82AkO9LJvG3YZimoYr5V28u9/FvKS+dFs9yIFALdFvGwrFnl9kXSHY9RQ36TpA== X-Received: by 2002:a05:600c:21c2:b0:40a:463c:1d8c with SMTP id x2-20020a05600c21c200b0040a463c1d8cmr9954922wmj.21.1700048820238; Wed, 15 Nov 2023 03:47:00 -0800 (PST) Received: from localhost ([2a01:4b00:d307:1000:f1d3:eb5e:11f4:a7d9]) by smtp.gmail.com with ESMTPSA id d1-20020a5d6441000000b0032f7f4d008dsm10375823wrw.20.2023.11.15.03.46.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Nov 2023 03:46:59 -0800 (PST) From: luca.boccassi@gmail.com To: dpdk stable Cc: Akhil Goyal , Ashish Gupta , Ciara Power , Declan Doherty , Fan Zhang , Gowrishankar Muthukrishnan , Kai Ji , Shally Verma , Sunila Sahu Subject: please help backporting some patches to stable release 20.11.10 Date: Wed, 15 Nov 2023 11:46:55 +0000 Message-Id: <20231115114655.2355923-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/11/22. 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 --- 47a85dda3f Ciara Power crypto/openssl: fix memory leaks in asym session 9d91c3047d Gowrishankar Muthukrishnan crypto/openssl: fix memory leaks in asym operations