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 CB775A0093 for ; Wed, 9 Mar 2022 01:14:08 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9C04340395; Wed, 9 Mar 2022 01:14:08 +0100 (CET) Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) by mails.dpdk.org (Postfix) with ESMTP id 3BCA240395 for ; Wed, 9 Mar 2022 01:14:07 +0100 (CET) Received: by mail-lf1-f51.google.com with SMTP id s25so853119lfs.10 for ; Tue, 08 Mar 2022 16:14:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cX0fn1LxNDcCIAMQ46daG07tNsIdIxx5pomib7up2Cg=; b=PswFWg21098wV47hMicNDvntOemiKJ+aGWfgZL3u73GzVZzOAUUU9QPJruUdXdVrW8 2xCNZzyoQabNBvsAepJ72f3QWWzE0egzlWe6UNesqdSOE6NhW43yNbjx3JjZL1lTzv/Q w5mcws7l0stIG1419nuftOCqfC+6+XkIJWgQkfPR+sr6cLerv35iIMPrn+onj3i28b4l /y10nbYL8MkKMKLi62zekvJhZrNQ+6+f6sZbuQ25nkapf2ajWYhQumu8zruY5ewp16KM YQsVx9wlEZIEJKPbOrZH8E8eD/rHr8ABg/u2WfUpCl2UpW6yzZgJ9lMEEXNmliRyO65u 4pMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cX0fn1LxNDcCIAMQ46daG07tNsIdIxx5pomib7up2Cg=; b=NUVQw0wIAnbEcmpTGNllBR0zUMnythvdV2ooy8lsibIrrD/ggxWr1zHSso+rb52GIT x/90TDODiTxP2U/vFn2f6GIKOIzIN2ZnnkLSdYidusdTPP5tygRmZuvspjlQZfg+5Awe owUM1sGqFI+LrL8G7adkEAB7Es3/2K1OD2jMFNilld2eDWFYTxJi4RL7mEZolKedgh52 FBaTBFSqs1m91XZdKqLpj/AX0H2Cz4WK+YF9bYnuxf1qHTS4H/XfRuPqlFDeuGVI1BYn GEQxWKjUgpsDmGlVnJnm3A7rAKHDtVDaxX7qpexjwLTrDQUrB0VFaxYrI3ht9KKPShCM pZHQ== X-Gm-Message-State: AOAM531Hd3ITp2BGmG7ZmV39eff4EtzQCiMJOV7nVBV+NNcruVG2mNHp lZhEKpOfya2YVAeiWvCBAlZY1281fbhT8x8plsw= X-Google-Smtp-Source: ABdhPJzkUj3jOVLzN7iZGZjaWg70/dvD1UwxGu4GIedeuAnefyvbKoJzPTHbex7HhzPbmygUBLuHHd5JaWPWsm3Gevg= X-Received: by 2002:a19:9201:0:b0:443:c317:98ff with SMTP id u1-20020a199201000000b00443c31798ffmr12347370lfd.331.1646784846515; Tue, 08 Mar 2022 16:14:06 -0800 (PST) MIME-Version: 1.0 References: <20220228213116.3344280-1-luca.boccassi@gmail.com> <20220228213154.3344354-1-luca.boccassi@gmail.com> In-Reply-To: From: Luca Boccassi Date: Wed, 9 Mar 2022 00:13:55 +0000 Message-ID: Subject: Re: please help backporting some patches to stable release 20.11.5 To: "De Lara Guarch, Pablo" Cc: dpdk stable Content-Type: text/plain; charset="UTF-8" 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 On Tue, 8 Mar 2022 at 17:44, De Lara Guarch, Pablo wrote: > > Hi Luca, > > > -----Original Message----- > > From: luca.boccassi@gmail.com > > Sent: Monday, February 28, 2022 9:32 PM > > Cc: Akhil Goyal ; Chengwen Feng > > ; Zhang, Roy Fan ; > > Laatz, Kevin ; Khoa To ; Matan > > Azrad ; Michael Baum ; De Lara > > Guarch, Pablo ; Shahaf Shuler > > ; Tal Shnaiderman ; Viacheslav > > Ovsiienko ; Yongseok Koh > > Subject: please help backporting some patches to stable release 20.11.5 > > > > 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 20.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 20.11 branch, or > > - Indicate that the patch should not be backported > > > > Please do either of the above by 03/07/22. > > > > You can find the a temporary work-in-progress branch of the coming 20.11.5 > > release at: > > https://github.com/bluca/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 20.11] foo/bar: fix baz > > > > With git format-patch, this can be achieved by appending the parameter: > > --subject-prefix='PATCH 20.11' > > > > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". > > > > FYI, branch 20.11 is located at tree: > > https://git.dpdk.org/dpdk-stable > > > > Thanks. > > > > Luca Boccassi > > > > --- > > 033904450b Chengwen Feng dma/hisilicon: use common PCI device naming > > 6be4c57add Michael Baum net/mlx5: fix errno update in shared context > > creation > > dcbaafdc8f Michael Baum net/mlx5: fix sibling device config check > > a501609ea6 Pablo de Lara crypto/ipsec_mb: fix length and offset settings > > Apologies, but looks like the commit "crypto/ipsec_mb: fix length and offset settings" > Has introduced a bug which I am fixing now. I will send a fix to the dev list soon, > but I am wondering if it's better to combine it into a single one and push it to the stable list instead of backporting two commits? Hi, Please send the fix separately, so that we can better track the main branch version. If the fix doesn't get into 22.03, we can postpone both backports until the next stable release, to avoid introducing regressions. Kind regards, Luca Boccassi