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 0CF5AA0547 for ; Fri, 11 Nov 2022 19:44:56 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EC9384014F; Fri, 11 Nov 2022 19:44:55 +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 A522640141 for ; Fri, 11 Nov 2022 19:44:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1668192293; 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=7Am4KQRpz1mmrL9JNQeGC+x5HvMHmaRCe53wbaV3VWY=; b=Y7m28uthM92OdXqDQZrDfgAWgBheqRdgi0r1T4+Xv7REQVNWfYImRCTiV9bgFNsI5emF3y df5nom0GPUQDhHbpeyt7M06DYmsXyz88rIqJMkdJqbLH4SDJJHBaMjCwyAz9R9zviC7IzS YCmFZ5L47VqKdC7o+ZbjiBLJ9E/Eo+Y= 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-5-8kmCB5I3Pl2f8eiOA0XmoA-1; Fri, 11 Nov 2022 13:44:51 -0500 X-MC-Unique: 8kmCB5I3Pl2f8eiOA0XmoA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id F0A35185A792; Fri, 11 Nov 2022 18:44:49 +0000 (UTC) Received: from rh.redhat.com (unknown [10.39.195.104]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3667340C955A; Fri, 11 Nov 2022 18:44:43 +0000 (UTC) From: Kevin Traynor To: dpdk stable Cc: Andrew Rybchenko , Chenbo Xia , David Marchand , Dongdong Liu , Hanumanth Pothula , Harman Kalra , Hernan Vargas , Huisong Li , Ivan Malov , Maxime Coquelin , Nithin Dabilpuram , Pavan Nikhilesh , Qi Zhang , Raslan Darawsheh , Shijith Thotton , Steve Yang , Sunil Kumar Kori , Thomas Monjalon , Wei Ling , Wenwu Ma Subject: please help backporting some patches to stable release 21.11.3 Date: Fri, 11 Nov 2022 18:44:33 +0000 Message-Id: <20221111184433.326109-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true 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 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 11/17/22. You can find the a temporary work-in-progress branch of the coming 21.11.3 release at: https://github.com/kevintraynor/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 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 --- d4cbbee345 David Marchand trace: fix metadata dump 5a0f64d84b Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx queues 59ceaa72d5 Harman Kalra common/cnxk: fix part number for CN10K 6f3325bbfa Hernan Vargas baseband/acc100: add LDPC encoder padding function 2df5fe2023 Hernan Vargas baseband/acc100: check AQ availability 5802f36dd4 Hernan Vargas baseband/acc100: enforce additional check on FCW 75114f78cf Hernan Vargas baseband/acc100: fix null HARQ input case c24d53b4cc Hernan Vargas baseband/acc100: fix ring availability calculation e23491fc2e Hernan Vargas baseband/acc100: fix ring/queue allocation a35799625e Huisong Li net/hns3: fix lock protection of RSS flow rule 1042ed401f Huisong Li net/hns3: fix restore filter function input 0d81da2559 Huisong Li net/hns3: fix RSS rule restore df810d1b6e Ivan Malov net/bonding: fix flow flush order on close 5781638519 Nithin Dabilpuram common/cnxk: fix RQ mask config for CN10KB chip 3fe71706ab Pavan Nikhilesh event/cnxk: fix stale data in workslot 927cb43fe9 Pavan Nikhilesh examples/l3fwd: fix port group mask with AltiVec 0b241667cc Steve Yang net/iavf: fix tainted scalar 133c67cfd7 Thomas Monjalon doc: add Rx buffer split capability for mlx5 40abb903fe Wenwu Ma examples/vhost: fix use after free