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 2A159A04FF for ; Mon, 21 Mar 2022 17:02:45 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0151C4161A; Mon, 21 Mar 2022 17:02:45 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 7C88D4161A for ; Mon, 21 Mar 2022 17:02:44 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1647878563; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=pzd8oKLCASIUtG+Q1W+3CmNOE50wHKhXyLZ6qK4LVOw=; b=X9vjfY3AK1DSQguBby6QF8dw0QqtFFAgm+UUYxhA1yI+vlVPCA+cdk7nJ/MUX3aYXdcf++ hpX4RrfhjIDf90SMSNqpkvbR9sxhxp0E+jVnelxvCPrUL+PMdhHCfj0lLu+95mR+eTc65w TLJJeJlbB4h4XnNyNVEgb2a/5COOAAI= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-675-DzhcwDxFNuSkr6SSlXLVRQ-1; Mon, 21 Mar 2022 12:02:40 -0400 X-MC-Unique: DzhcwDxFNuSkr6SSlXLVRQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id ACC77185A7BA; Mon, 21 Mar 2022 16:02:39 +0000 (UTC) Received: from rh.Home (unknown [10.39.195.33]) by smtp.corp.redhat.com (Postfix) with ESMTP id 21514C23DC6; Mon, 21 Mar 2022 16:02:37 +0000 (UTC) From: Kevin Traynor To: dpdk stable Cc: Daxue Gao , Fan Zhang , Jerin Jacob , Pablo de Lara , Radu Nicolau , Rakesh Kudurumalla Subject: please help backporting some patches to stable release 21.11.1 Date: Mon, 21 Mar 2022 16:02:27 +0000 Message-Id: <20220321160227.70100-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ktraynor@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII" 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), I didn't apply following commits from DPDK main to 21.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 21.11 branch, or - Indicate that the patch should not be backported Please do either of the above by 03/23/22. 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 21.11] foo/bar: fix baz With git format-patch, this can be achieved by appending the parameter: --subject-prefix='PATCH 21.11' Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". FYI, branch 21.11 is located at tree: https://git.dpdk.org/dpdk-stable Thanks. Kevin --- a501609ea6 Pablo de Lara crypto/ipsec_mb: fix length and offset settings 837269c2e5 Pablo de Lara crypto/ipsec_mb: fix GMAC parameters setting 68f8a52a6b Rakesh Kudurumalla net/cnxk: fix build with optimization