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 B399F455D8 for ; Tue, 16 Jul 2024 12:30:17 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AE7C340B94; Tue, 16 Jul 2024 12:30:17 +0200 (CEST) Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) by mails.dpdk.org (Postfix) with ESMTP id 13AFD402AD for ; Tue, 16 Jul 2024 12:30:16 +0200 (CEST) Received: by mail-yb1-f170.google.com with SMTP id 3f1490d57ef6-e035f4e3473so4844651276.3 for ; Tue, 16 Jul 2024 03:30:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721125815; x=1721730615; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=OVHAvvV8kwlZqjC789/TF5RTgjBsPbkC+PRFnxp9D8k=; b=G32jWPWYE16ZEWX5tviF5hgimto439EKJKxVZZHWSe+2SaKxVRi5+a+TL7GQV4Aynk 2OBZl5GW0UyhoNb2JzvAxfaHuRRAG7wpydtYQ3AH8U34irjaPf58CXX+CAbJzRzZfbv6 QZJK5zKt98xHgj4bsEIrWBmJh1pt2OyVWHkq+mOU4aVh6XN2+2z/yKT8APFaCjWHjXdq dj6lLGJqN/pLgnxulOFXl8PfCJnJ7GxF/q31DaMTQCkQrAks2xmYhDX/pxtJwo7xH1sG YYegMdfNxtgjCnjhAf12yIxPQYdzrQ6OgoxCr/bimlSq81D/DplZStTH7641NAGh7cI7 DwvQ== X-Gm-Message-State: AOJu0YwnU9KRdXGw0PT61xJzT2v/sTGOUBTIW2+1YFtY2st1jyXDkM0J +WKTnP+DRk6M/+YlYSdzMAXs1OMMVNKNcxqP4+BMQ4e8YJeDFZQxrN5OSKLRcW4= X-Google-Smtp-Source: AGHT+IGUKy9Aj+xkYQXBSYOKua4RX2Q6KUOsmqPNHZFRCqV3FGj4VoGPU+mq1BQvBJtYS+5HUvP5tw== X-Received: by 2002:a05:6902:1244:b0:e03:46ae:f277 with SMTP id 3f1490d57ef6-e05d5667f67mr1883412276.3.1721125815244; Tue, 16 Jul 2024 03:30:15 -0700 (PDT) Received: from mail-yw1-f169.google.com (mail-yw1-f169.google.com. [209.85.128.169]) by smtp.gmail.com with ESMTPSA id 3f1490d57ef6-e05a46fe420sm1253182276.51.2024.07.16.03.30.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jul 2024 03:30:14 -0700 (PDT) Received: by mail-yw1-f169.google.com with SMTP id 00721157ae682-65fa21206b5so25262477b3.3 for ; Tue, 16 Jul 2024 03:30:14 -0700 (PDT) X-Received: by 2002:a0d:dac3:0:b0:660:b8fa:aed6 with SMTP id 00721157ae682-6637fd63379mr20084187b3.27.1721125814664; Tue, 16 Jul 2024 03:30:14 -0700 (PDT) MIME-Version: 1.0 References: <20240715153259.2231242-1-luca.boccassi@gmail.com> In-Reply-To: From: Luca Boccassi Date: Tue, 16 Jul 2024 11:30:03 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: please help backporting some patches to stable release 22.11.6 To: "Du, Frank" Cc: dpdk stable Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Hi, That mempool patch introduces a new API, so it is not appropriate for backporting. If you need this bug fix in 22.11.6, then a 22.11.x specific patch is needed for it, that doesn't change the library API. On Tue, 16 Jul 2024 at 03:44, Du, Frank wrote: > > Hi Luca, > > For this one: > 97039941b2 Frank Du net/af_xdp: parse UMEM map info from mempool > > It depends on another mempool patch: https://github.com/DPDK/dpdk/commit/= 2f1015d8d56d32465cc260faf469950ebb9cf73b > > I guess it can pass the build if the dependency patch is cherry-picked al= so. > > Thanks, > Frank > > > -----Original Message----- > > From: luca.boccassi@gmail.com > > Sent: Monday, July 15, 2024 11:33 PM > > To: dpdk stable > > Cc: Richardson, Bruce ; Chaoyong He > > ; Loftus, Ciara ; Fer= ruh > > Yigit ; Du, Frank ; Stokes, I= an > > ; Keller, Jacob E ; Laa= tz, Kevin > > ; Kiran Kumar K ; Long = Wu > > ; Morten Br=C3=B8rup ; > > Niklas S=C3=B6derlund ; Nithin Dabilpura= m > > ; Stillwell Jr, Paul M > > ; Peng Zhang ; = Yang, > > Qiming ; Zhang, Qi Z ; Rah= ul > > Bhansali ; Ray Kinsella ; Satha R= ao > > ; Satheesh Paul ; Sunil > > Kumar Kori ; Xiaolong Ye > > Subject: please help backporting some patches to stable release 22.11.6 > > > > 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 22.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 22.11 branch, or > > - Indicate that the patch should not be backported > > > > Please do either of the above by 07/22/24. > > > > You can find the a temporary work-in-progress branch of the coming 22.1= 1.6 > > release at: > > https://github.com/bluca/dpdk-stable > > It is recommended to backport on top of that to minimize further confli= cts 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=3D18.11&id=3Dd90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb > > > > When sending the backported patch, please indicate the target branch in= the > > subject line, as we have multiple branches, for example: > > [PATCH 22.11] foo/bar: fix baz > > > > With git format-patch, this can be achieved by appending the parameter: > > --subject-prefix=3D'PATCH 22.11' > > > > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". > > > > FYI, branch 22.11 is located at tree: > > https://git.dpdk.org/dpdk-stable > > > > Thanks. > > > > Luca Boccassi > > > > --- > > 97039941b2 Frank Du net/af_xdp: parse UMEM map info from mempo= ol > > ab1bb0c402 Peng Zhang net/nfp: add check for numbers of VF repre= sentor > > port > > fde2a1cb34 Rahul Bhansali net/cnxk: postpone disabling NPC Rx and MC= AM