From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Huisong Li <lihuisong@huawei.com>
Cc: stable@dpdk.org, liudongdong3@huawei.com,
fengchengwen@huawei.com, huangdaode@huawei.com
Subject: Re: [PATCH 19.11 0/2] backport two patches for bonding and hns3 driver
Date: Mon, 5 Dec 2022 07:55:06 +0100 [thread overview]
Message-ID: <CAATJJ0LZ_=qXGs2+iJzkQxiYp1bEOZaNr-oj=JWj=J6G=2DPvg@mail.gmail.com> (raw)
In-Reply-To: <20221201060826.55104-1-lihuisong@huawei.com>
On Thu, Dec 1, 2022 at 7:08 AM Huisong Li <lihuisong@huawei.com> wrote:
>
> Fix slave device Rx/Tx offload configuration for bonding driver and delete
> unused markup for hns3 driver.
>
> Huisong Li (2):
> net/bonding: fix slave device Rx/Tx offload configuration
> net/hns3: delete unused markup
Hi Huisong,
unfortunately your backports arrived after -rc1 was tagged and I' not
like to reset testing for everyone.
I'll keep them open - if anything else is severe enough to reset to an
-rc2 anyway I'll happily apply them.
Otherwise I'll queue them for when there is another release,
but honestly that isn't sure as 19.11.14 was meant to be the last
normal stable release of the 19.11.x series.
> drivers/net/bonding/rte_eth_bond_pmd.c | 11 ++++-------
> drivers/net/hns3/hns3_stats.c | 23 ++++++-----------------
> 2 files changed, 10 insertions(+), 24 deletions(-)
>
> --
> 2.33.0
>
--
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2022-12-05 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 6:08 Huisong Li
2022-12-01 6:08 ` [PATCH 19.11 1/2] net/bonding: fix slave device Rx/Tx offload configuration Huisong Li
2022-12-01 6:08 ` [PATCH 19.11 2/2] net/hns3: delete unused markup Huisong Li
2022-12-05 6:55 ` Christian Ehrhardt [this message]
2022-12-06 1:27 ` [PATCH 19.11 0/2] backport two patches for bonding and hns3 driver lihuisong (C)
2022-12-06 6:43 ` Christian Ehrhardt
2022-12-06 6:54 ` lihuisong (C)
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='CAATJJ0LZ_=qXGs2+iJzkQxiYp1bEOZaNr-oj=JWj=J6G=2DPvg@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=fengchengwen@huawei.com \
--cc=huangdaode@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.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).