patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Ding, Xuan" <xuan.ding@intel.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 19.11.11
Date: Mon, 6 Dec 2021 08:12:28 +0000	[thread overview]
Message-ID: <BN9PR11MB5513B1103D4A459B726C88DCE76D9@BN9PR11MB5513.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAATJJ0J8w73+na0876T9J=HrOMGAaRVqKWA1qg14e9nrfq_A2A@mail.gmail.com>

Hi Christian,

>-----Original Message-----
>From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>Sent: Friday, December 3, 2021 2:27 PM
>To: Ding, Xuan <xuan.ding@intel.com>
>Cc: stable@dpdk.org
>Subject: Re: please help backporting some patches to stable release 19.11.11
>
>On Fri, Dec 3, 2021 at 3:07 AM Ding, Xuan <xuan.ding@intel.com> wrote:
>>
>> Hi Christian,
>>
>> The two fix patches from mine aimed at DPDK version after 19.11. So they
>only need to be backported in 20.11.
>> 04bcc80204  Xuan Ding        net/virtio: fix indirect descriptor reconnection
>> ad6f01945a  Xuan Ding        net/virtio: fix avail descriptor ID
>
>Thank you,
>they both refer to fix a patch that in turn fixes issues that existed before 19.11.
>Hence they came into the candidate list.
>
>For the second one you are right, this isn't present, but 04bcc80204 refers to
>fix 8c1df884.
>And 8c1df884 is in 19.11.x as:
>
>commit 8c1df8846b15bf87beee2907dd9ecb5d5adaca1d
>Author: Marvin Liu <yong.liu@intel.com>
>Date:   Mon Sep 28 16:20:51 2020 +0800
>
>    net/virtio: fix packed ring indirect descricptors setup
>
>    [ upstream commit 381f39ebb78a35d8dcc2d4500419644c7de5400f ]
>
>
>So do we really not need/want it?

Thanks for your confirmation.
For 04bcc80204, I will send out a patch.
BTW, ad6f01945a refers to b473061b0e1d ("net/virtio: fix indirect descriptors in packed datapaths").
Why hasn't this patch been backported in 19.11?

Regards,
Xuan

>
>> Thanks for your reminder.
>>
>> Regards,
>> Xuan
>
>
>--
>Christian Ehrhardt
>Staff Engineer, Ubuntu Server
>Canonical Ltd

  reply	other threads:[~2021-12-06  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211130165621.2467243-1-christian.ehrhardt@canonical.com>
     [not found] ` <CAATJJ0+ndH8WxJUisy4aJhxX3=o+K_KjGqCdJzp7tKOwtFs0yw@mail.gmail.com>
2021-12-02 20:18   ` Maxime Coquelin
2021-12-03  6:22     ` Christian Ehrhardt
2021-12-03  2:07   ` Ding, Xuan
2021-12-03  6:27     ` Christian Ehrhardt
2021-12-06  8:12       ` Ding, Xuan [this message]
2021-12-06 14:27         ` Christian Ehrhardt
2021-12-07  8:47           ` Ding, Xuan
2021-12-03  8:58 ` [PATCH 19.11] net/mlx5: fix Altivec Rx Xueming Li
2021-12-06  8:26   ` Christian Ehrhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BN9PR11MB5513B1103D4A459B726C88DCE76D9@BN9PR11MB5513.namprd11.prod.outlook.com \
    --to=xuan.ding@intel.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).