From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
dpdk stable <stable@dpdk.org>
Cc: Jiawei Wang <jiaweiw@nvidia.com>,
Lance Richardson <lance.richardson@broadcom.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"Yang, MurphyX" <murphyx.yang@intel.com>,
Shiri Kuzin <shirik@nvidia.com>,
"Yang, SteveX" <stevex.yang@intel.com>,
Suanming Mou <suanmingm@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.7
Date: Fri, 12 Feb 2021 09:16:49 +0000 [thread overview]
Message-ID: <720d476a96124323b259d4c70d4d7677@intel.com> (raw)
In-Reply-To: <CAATJJ0+P34zXGimByiFDM_ATGJjLAJSmBCm77bkbJ3GZ4R0HDQ@mail.gmail.com>
No problem, Christian, happy to help, and thank you for doing the work of pulling together the LTS release.
> -----Original Message-----
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Sent: Friday, February 12, 2021 8:12 AM
> To: dpdk stable <stable@dpdk.org>
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; Jiawei Wang
> <jiaweiw@nvidia.com>; Lance Richardson <lance.richardson@broadcom.com>;
> Min Hu (Connor) <humin29@huawei.com>; Yang, MurphyX
> <murphyx.yang@intel.com>; Shiri Kuzin <shirik@nvidia.com>; Yang, SteveX
> <stevex.yang@intel.com>; Suanming Mou <suanmingm@nvidia.com>; Tal
> Shnaiderman <talshn@nvidia.com>; Luca Boccassi <bluca@debian.org>
> Subject: Re: please help backporting some patches to stable release
> 19.11.7
>
> Hi everyone,
> I wanted to use this chance to send my thanks to so many participating
> people.
> So far I've got some feedback about patches I don't need to care for
> 19.11.7 (thanks).
> But even more important we've had 9 active contributors providing 14
> backports already.
> Looking at past releases that is a good amount of feedback.
> And while I know that a good project is never built on just a few
> people, I still wanted
> to use the chance to thank the following people for their help on
> towards 19.11.7:
>
> Bruce Richardson <bruce.richardson@intel.com>
> Jiawei Wang <jiaweiw@nvidia.com>
> Lance Richardson <lance.richardson@broadcom.com>
> Min Hu (Connor) <humin29@huawei.com>
> Murphy Yang <murphyx.yang@intel.com>
> Shiri Kuzin <shirik@nvidia.com>
> Steve Yang <stevex.yang@intel.com>
> Suanming Mou <suanmingm@nvidia.com>
> Tal Shnaiderman <talshn@nvidia.com>
>
> Kind Regards,
> Christian
>
> P.S. github.com:cpaelzer/dpdk-stable-queue.git is updated with the
> above and I'm looking forward to further finalize this once 21.02 is
> released.
>
> On Mon, Feb 8, 2021 at 5:39 PM Lance Richardson
> <lance.richardson@broadcom.com> wrote:
> >
> > I have posted these:
> >
> > 73d1cc96be Lance Richardson net/bnxt: fix doorbell write ordering
> > c86e930165 Lance Richardson net/bnxt: fix fallback mbuf allocation
> logic
> > e750acef45 Lance Richardson net/bnxt: fix outer UDP checksum Rx
> > offload capability
> >
> > These are dependent on a number of changes that are only present in
> > 20.11 and later, I don't think they are good candidates for back-
> porting:
> >
> > d5bbd72246 Lance Richardson net/bnxt: make offload flags mapping per-
> ring
> > 48a580c5df Lance Richardson net/bnxt: set correct checksum status in
> mbuf
>
>
>
> --
> Christian Ehrhardt
> Staff Engineer, Ubuntu Server
> Canonical Ltd
next prev parent reply other threads:[~2021-02-12 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210204115554.2506672-1-christian.ehrhardt@canonical.com>
2021-02-04 13:44 ` [dpdk-stable] [EXT] " Liron Himi
2021-02-04 14:43 ` [dpdk-stable] " Richardson, Bruce
2021-02-04 16:59 ` Maxime Coquelin
2021-02-04 20:16 ` Dmitry Kozlyuk
2021-02-08 16:39 ` Lance Richardson
2021-02-12 8:11 ` Christian Ehrhardt
2021-02-12 9:16 ` Richardson, Bruce [this message]
2021-02-12 14:38 ` Slava Ovsiienko
2021-02-19 8:18 ` Somnath Kotur
[not found] <20210215133002.1856070-1-christian.ehrhardt@canonical.com>
2021-02-19 6:23 ` [dpdk-stable] 回复: " Feifei Wang
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=720d476a96124323b259d4c70d4d7677@intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=humin29@huawei.com \
--cc=jiaweiw@nvidia.com \
--cc=lance.richardson@broadcom.com \
--cc=murphyx.yang@intel.com \
--cc=shirik@nvidia.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@intel.com \
--cc=suanmingm@nvidia.com \
--cc=talshn@nvidia.com \
/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).