From: Lance Richardson <lance.richardson@broadcom.com>
To: dpdk stable <stable@dpdk.org>, christian.ehrhardt@canonical.com
Cc: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.7
Date: Mon, 8 Feb 2021 11:39:05 -0500 [thread overview]
Message-ID: <CADyeNEBB6HxpNFspqCUvoVqMmnZYykPAkhifyd_+1b0OFichbQ@mail.gmail.com> (raw)
In-Reply-To: <20210204115554.2506672-1-christian.ehrhardt@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
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
next prev parent reply other threads:[~2021-02-08 16:39 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 [this message]
2021-02-12 8:11 ` Christian Ehrhardt
2021-02-12 9:16 ` Richardson, Bruce
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=CADyeNEBB6HxpNFspqCUvoVqMmnZYykPAkhifyd_+1b0OFichbQ@mail.gmail.com \
--to=lance.richardson@broadcom.com \
--cc=ajit.khaparde@broadcom.com \
--cc=christian.ehrhardt@canonical.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=venkatkumar.duvvuru@broadcom.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).