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 36DCAA04FF for ; Mon, 21 Mar 2022 10:08:55 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E1EEF41614; Mon, 21 Mar 2022 10:08:54 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id D141D41614 for ; Mon, 21 Mar 2022 10:08:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1647853733; x=1679389733; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=cszEE+ygwiOyXGYpid1u3svhd6/N6/keBuPTDii0kZM=; b=mGIdElehYbUBgkJOW2JWCwpoG92ZkAOaO6lSNyk8jlztuwZQxQcX9lib s+/5Tt0K7FbA+xqECvqv67Gj4eeU9M0C6G2Pln5zPjbPPeEa1yjcwqlcN w7gSqVox7HWr/zsVfjShTjDAXV2nMQ6w5UgMcz4mq3RAIh07sKU0yXy55 YYCDSr07lEdApyPDiJMf9sSQdiXXEZHnbSiCGzC79JZY56Adza0cx8V8O 4IDK1wFCpDgika+6f+DvVCK37Y2LUf5NXs/QHS3UZHnXYfGCvq9yGMJzQ 3SXOiZVX8uI6AD2qL3rv1OwKeyPAks7q+lhPt7t4xNOD3F3QCIIyISi6v A==; X-IronPort-AV: E=McAfee;i="6200,9189,10292"; a="237449053" X-IronPort-AV: E=Sophos;i="5.90,198,1643702400"; d="scan'208";a="237449053" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Mar 2022 02:08:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,198,1643702400"; d="scan'208";a="646536928" Received: from irsmsx601.ger.corp.intel.com ([163.33.146.7]) by fmsmga002.fm.intel.com with ESMTP; 21 Mar 2022 02:08:51 -0700 Received: from irsmsx601.ger.corp.intel.com (163.33.146.7) by irsmsx601.ger.corp.intel.com (163.33.146.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Mon, 21 Mar 2022 09:08:50 +0000 Received: from irsmsx601.ger.corp.intel.com ([163.33.146.7]) by irsmsx601.ger.corp.intel.com ([163.33.146.7]) with mapi id 15.01.2308.021; Mon, 21 Mar 2022 09:08:50 +0000 From: "Richardson, Bruce" To: dpdk stable Subject: RE: please help backporting some patches to stable release 19.11.12 Thread-Topic: please help backporting some patches to stable release 19.11.12 Thread-Index: AQHYOgnVtD1M38/n2Uu3F9xD9jh0J6zJkgZw Date: Mon, 21 Mar 2022 09:08:50 +0000 Message-ID: References: <20220317141727.1954868-1-christian.ehrhardt@canonical.com> In-Reply-To: <20220317141727.1954868-1-christian.ehrhardt@canonical.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-version: 11.6.401.20 dlp-product: dlpe-windows dlp-reaction: no-action x-originating-ip: [163.33.253.164] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: , Errors-To: stable-bounces@dpdk.org > -----Original Message----- > From: christian.ehrhardt@canonical.com > Sent: Thursday, March 17, 2022 2:17 PM > Cc: Singh, Aman Deep ; Iremonger, Bernard > ; Richardson, Bruce > ; Yigit, Ferruh ; > Gregory Etelson ; Wu, Jingjing > ; Mcnamara, John ; > Kovacevic, Marko ; Xu, Ting > ; Lu, Wenzhuo > Subject: please help backporting some patches to stable release 19.11.12 >=20 > Hi commit authors (and maintainers), >=20 > Despite being selected by the DPDK maintenance tool ./devtools/git-log- > fixes.sh > I didn't apply following commits from DPDK main to 19.11 > stable branch, as conflicts or build errors occur. >=20 > Can authors check your patches in the following list and either: > - Backport your patches to the 19.11 branch, or > - Indicate that the patch should not be backported >=20 > Please do either of the above by 03/20/22. >=20 > You can find the a temporary work-in-progress branch of the coming > 19.11.12 > release at: > https://github.com/cpaelzer/dpdk-stable-queue > It is recommended to backport on top of that to minimize further conflict= s > or > misunderstandings. >=20 > Some notes on stable backports: >=20 > A backport should contain a reference to the DPDK main branch commit > in it's commit message in the following fashion: > [ upstream commit ] >=20 > For example: > https://git.dpdk.org/dpdk- > stable/commit/?h=3D18.11&id=3Dd90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb >=20 > When sending the backported patch, please indicate the target branch in > the > subject line, as we have multiple branches, for example: > [PATCH 19.11] foo/bar: fix baz >=20 > With git format-patch, this can be achieved by appending the parameter: > --subject-prefix=3D'PATCH 19.11' >=20 > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". >=20 > FYI, branch 19.11 is located at tree: > https://git.dpdk.org/dpdk-stable >=20 > Thanks. >=20 > Christian Ehrhardt >=20 > --- > c265d58619 Bruce Richardson doc: replace characters for (R) symbol in > Linux guide > a058de216c Gregory Etelson app/testpmd: fix GTP header parsing in > checksum engine Hi, I am not sure that my doc fix is worth backporting. If I get the chance I w= ill do a new version of it, but if it is not backported no serious issues w= ill occur as the docs seem fine without it. It's more a convenience for dev= elopers. /Bruce