From: Jakub Kicinski <kuba@kernel.org>
To: Jijie Shao <shaojijie@huawei.com>
Cc: <yisen.zhuang@huawei.com>, <salil.mehta@huawei.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<horms@kernel.org>, <shenjian15@huawei.com>,
<wangjie125@huawei.com>, <liuyonglong@huawei.com>,
<lanhao@huawei.com>, <wangpeiyang1@huawei.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 net-next 0/4] There are some features for the HNS3 ethernet driver
Date: Thu, 4 Jan 2024 07:48:43 -0800 [thread overview]
Message-ID: <20240104074843.29021784@kernel.org> (raw)
In-Reply-To: <7f561916-a7ad-4189-b3a7-dfe43f9daeaa@huawei.com>
On Thu, 4 Jan 2024 19:17:35 +0800 Jijie Shao wrote:
> Excuse me, This series has not been applied for a long time.
>
> Is there any problem with this series?
It got marked as Changes Requested over the winter shutdown / break.
I'm not exactly sure why, to be honest. Please repost.
next prev parent reply other threads:[~2024-01-04 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 1:35 [PATCH V4 net-next 0/4] There are some features for the HNS3 ethernet driver Jijie Shao
2023-12-19 1:35 ` [PATCH V4 net-next 1/4] net: hns3: add command queue trace for hns3 Jijie Shao
2023-12-19 1:35 ` [PATCH V4 net-next 2/4] net: hns3: move constants from hclge_debugfs.h to hclge_debugfs.c Jijie Shao
2023-12-19 11:14 ` Simon Horman
2023-12-19 1:35 ` [PATCH V4 net-next 3/4] net: hns3: dump more reg info based on ras mod Jijie Shao
2023-12-19 11:18 ` Simon Horman
2023-12-19 1:35 ` [PATCH V4 net-next 4/4] net: hns3: support dump pfc frame statistics in tx timeout log Jijie Shao
2024-01-04 11:17 ` [PATCH V4 net-next 0/4] There are some features for the HNS3 ethernet driver Jijie Shao
2024-01-04 15:48 ` Jakub Kicinski [this message]
2024-01-05 1:11 ` Jijie Shao
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 1:01 Jijie Shao
2024-01-05 9:50 ` Jiri Pirko
2024-01-09 8:20 ` 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=20240104074843.29021784@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=lanhao@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@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=wangpeiyang1@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.