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 743CCA00C3 for ; Tue, 21 Jun 2022 12:02:43 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6D1FA40151; Tue, 21 Jun 2022 12:02:43 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 86B4F40151 for ; Tue, 21 Jun 2022 12:02:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655805762; 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=WWhzjU9gsXXn3g+2ta0cv9r8YFyAzDSehCc4gw+JHpE=; b=dod5e4kMUUs08/fkI4MgNgtrzwgilLYpgpoo6mNUg/f/+pih8PByVD6t/1UBobqq5vMj6E SX1KsenvnPKsWWGTH7AfaOM8ldK1Tr9fZaWrIgr2akYCxlGszFbxCk+O8MTXng+6l+TRKu Grs2RG0ysynco0ZLPBziD/yC/BgtbTM= 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-100-FwirPVVXM0qhvGYY3N2R8A-1; Tue, 21 Jun 2022 06:02:38 -0400 X-MC-Unique: FwirPVVXM0qhvGYY3N2R8A-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 B8570801756; Tue, 21 Jun 2022 10:02:37 +0000 (UTC) Received: from rh.redhat.com (unknown [10.39.194.217]) by smtp.corp.redhat.com (Postfix) with ESMTP id 04B7840EC003; Tue, 21 Jun 2022 10:02:32 +0000 (UTC) From: Kevin Traynor To: dpdk stable Cc: Ajit Khaparde , Andrew Rybchenko , Chaoyong He , Chengwen Feng , Dariusz Sosnowski , Gagandeep Singh , Jerin Jacob , Jiawen Wu , Kalesh AP , Louis Peens , =?UTF-8?q?Morten=20Br=C3=B8rup?= , =?UTF-8?q?Niklas=20S=C3=B6derlund?= , Nithin Dabilpuram , Pavan Nikhilesh , Peng Zhang , Qi Zhang , Somnath Kotur , Viacheslav Ovsiienko , Walter Heymans , Yiding Zhou Subject: please help backporting some patches to stable release 21.11.2 Date: Tue, 21 Jun 2022 11:02:23 +0100 Message-Id: <20220621100223.1148243-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 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-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 06/23/22. You can find the a temporary work-in-progress branch of the coming 21.11.2 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 --- These commits have non-trivial conflicts while applying to 21.11 branch: d2fa2632a4 Dariusz Sosnowski net/mlx5: fix RSS hash types adjustment 13ce268103 Gagandeep Singh common/dpaax: remove dead code 708ebe7d03 Jiawen Wu net/ngbe: fix external PHY power down 6dcfb19f60 Jiawen Wu net/ngbe: fix reading M88E1512 PHY mode 696a821178 Jiawen Wu net/ngbe: redesign internal PHY init flow e2819fea94 Nithin Dabilpuram net/cnxk: fix multi-segment extraction in vwqe path 2e668c547f Nithin Dabilpuram net/cnxk: fix roundup size with transport mode 417be15e5f Peng Zhang net/nfp: make sure MTU is never larger than mbuf size These commits apply cleanly to 21.11 branch but cause build errors: 14124e48a3 Nithin Dabilpuram net/cnxk: fix hotplug detach for first device c0278f6e52 Kalesh AP net/bnxt: fix tunnel stateless offloads 485df8847a Chengwen Feng ethdev: clarify null location case in xstats get 676d986b4b Yiding Zhou net/iavf: fix crash after VF reset failure