From: Simon Horman <simon.horman@corigine.com>
To: Jijie Shao <shaojijie@huawei.com>
Cc: netdev@vger.kernel.org, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, lanhao@huawei.com,
chenhao418@huawei.com, wangjie125@huawei.com,
shenjian15@huawei.com
Subject: Re: [PATCH net 0/4] There are some bugfix for the HNS3 ethernet driver
Date: Fri, 21 Jul 2023 12:26:56 +0100 [thread overview]
Message-ID: <ZLprgMjesA9KQ667@corigine.com> (raw)
In-Reply-To: <20230720020510.2223815-1-shaojijie@huawei.com>
On Thu, Jul 20, 2023 at 10:05:06AM +0800, Jijie Shao wrote:
> There are some bugfix for the HNS3 ethernet driver
>
> Hao Lan (2):
> net: hns3: fix the imp capability bit cannot exceed 32 bits issue
> net: hns3: add tm flush when setting tm
>
> Jijie Shao (2):
> net: hns3: fix wrong tc bandwidth weight data issue
> net: hns3: fix wrong bw weight of disabled tc issue
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-07-21 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 2:05 [PATCH net 0/4] There are some bugfix for the HNS3 ethernet driver Jijie Shao
2023-07-20 2:05 ` [PATCH net 1/4] net: hns3: fix the imp capability bit cannot exceed 32 bits issue Jijie Shao
2023-07-20 2:05 ` [PATCH net 2/4] net: hns3: add tm flush when setting tm Jijie Shao
2023-07-20 2:05 ` [PATCH net 3/4] net: hns3: fix wrong tc bandwidth weight data issue Jijie Shao
2023-07-20 2:05 ` [PATCH net 4/4] net: hns3: fix wrong bw weight of disabled tc issue Jijie Shao
2023-07-21 11:26 ` Simon Horman [this message]
2023-07-24 8:40 ` [PATCH net 0/4] There are some bugfix for the HNS3 ethernet driver patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 9:30 Jijie Shao
2025-05-01 14:30 ` patchwork-bot+netdevbpf
2025-07-02 13:08 Jijie Shao
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=ZLprgMjesA9KQ667@corigine.com \
--to=simon.horman@corigine.com \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lanhao@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@huawei.com \
--cc=yisen.zhuang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.