From: "lihuisong (C)" <lihuisong@huawei.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.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: Tue, 6 Dec 2022 14:54:26 +0800 [thread overview]
Message-ID: <093eab56-32cc-9373-9db8-8a5fd8e88dc0@huawei.com> (raw)
In-Reply-To: <CAATJJ0L-TAiofHtBRPV=Um_nj0W1+qwgUOSkJE8ZafH-b5Jtww@mail.gmail.com>
在 2022/12/6 14:43, Christian Ehrhardt 写道:
> On Tue, Dec 6, 2022 at 2:27 AM lihuisong (C) <lihuisong@huawei.com> wrote:
>>
>> 在 2022/12/5 14:55, Christian Ehrhardt 写道:
>>> 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.
>> Sorry for my late backports.
>>> I'll keep them open - if anything else is severe enough to reset to an
>>> -rc2 anyway I'll happily apply them.
>> I thought there would be -rc2 later. Does the -rc version of LTS run
>> like this?
> Yeah, they are meant to be stable after all :-)
> We'd hope (but not always succeed) that all backports are fine on the first try.
>
> We usually try to only have -rc1 which becomes the release if passing
> verification without regressions to the older version.
>
> Any patches arriving late are always welcome and queued for either the
> next LTS release or at the next -rc if verification results trigger
> the need for that.
>
> And in addition the fact that this was meant to be the last normal
> 19.11.x LTS makes this a special case.
Got it. Thanks.
>
>>> 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.
>> Follow your plan. Thanks, Christian.😁
>>>> 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
>>>>
>
>
prev parent reply other threads:[~2022-12-06 6:54 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 ` [PATCH 19.11 0/2] backport two patches for bonding and hns3 driver Christian Ehrhardt
2022-12-06 1:27 ` lihuisong (C)
2022-12-06 6:43 ` Christian Ehrhardt
2022-12-06 6:54 ` lihuisong (C) [this message]
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=093eab56-32cc-9373-9db8-8a5fd8e88dc0@huawei.com \
--to=lihuisong@huawei.com \
--cc=christian.ehrhardt@canonical.com \
--cc=fengchengwen@huawei.com \
--cc=huangdaode@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).