From: Jijie Shao <shaojijie@huawei.com>
To: Jacob Keller <jacob.e.keller@intel.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>, <horms@kernel.org>
Cc: <shaojijie@huawei.com>, <shenjian15@huawei.com>,
<liuyonglong@huawei.com>, <chenhao418@huawei.com>,
<lantao5@huawei.com>, <huangdonghua3@h-partners.com>,
<yangshuaisong@h-partners.com>, <jonathan.cameron@huawei.com>,
<salil.mehta@huawei.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net 0/3] There are some bugfix for hibmcge ethernet driver
Date: Fri, 24 Oct 2025 15:24:53 +0800 [thread overview]
Message-ID: <f99d878c-abf3-41ae-ae7f-b1db4f205561@huawei.com> (raw)
In-Reply-To: <49a1be1b-36c2-463e-8684-8781d4654da8@intel.com>
on 2025/10/24 9:08, Jacob Keller wrote:
>
> On 10/21/2025 7:00 AM, Jijie Shao wrote:
>> This patch set is intended to fix several issues for hibmcge driver:
>> 1. Patch1 fixes the issue where buf avl irq is disabled after irq_handle.
>> 2. Patch2 eliminates the error logs in scenarios without phy.
>> 3. Patch3 fixes the issue where the network port becomes unusable
>> after a PCIe RAS event.
>>
>>
> We typically suggest using imperative wording for the subject such as
> "bug fixes for the hibmcge ethernet driver".
Ok, I will change in V2
Thanks,
Jijie Shao
>> Jijie Shao (3):
>> net: hibmcge: fix rx buf avl irq is not re-enabled in irq_handle issue
>> net: hibmcge: remove unnecessary check for np_link_fail in scenarios
>> without phy.
>> net: hibmcge: fix the inappropriate netif_device_detach()
>>
>> drivers/net/ethernet/hisilicon/hibmcge/hbg_common.h | 1 +
>> drivers/net/ethernet/hisilicon/hibmcge/hbg_err.c | 10 ++++++----
>> drivers/net/ethernet/hisilicon/hibmcge/hbg_hw.c | 3 +++
>> drivers/net/ethernet/hisilicon/hibmcge/hbg_irq.c | 1 +
>> drivers/net/ethernet/hisilicon/hibmcge/hbg_mdio.c | 1 -
>> 5 files changed, 11 insertions(+), 5 deletions(-)
>>
next prev parent reply other threads:[~2025-10-24 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 14:00 Jijie Shao
2025-10-21 14:00 ` [PATCH net 1/3] net: hibmcge: fix rx buf avl irq is not re-enabled in irq_handle issue Jijie Shao
2025-10-24 1:15 ` Jacob Keller
2025-10-24 6:39 ` Jijie Shao
2025-10-24 20:23 ` Jacob Keller
2025-10-21 14:00 ` [PATCH net 2/3] net: hibmcge: remove unnecessary check for np_link_fail in scenarios without phy Jijie Shao
2025-10-24 1:10 ` Jacob Keller
2025-10-24 6:44 ` Jijie Shao
2025-10-21 14:00 ` [PATCH net 3/3] net: hibmcge: fix the inappropriate netif_device_detach() Jijie Shao
2025-10-24 1:05 ` Jacob Keller
2025-10-24 7:21 ` Jijie Shao
2025-10-24 20:24 ` Jacob Keller
2025-10-24 1:08 ` [PATCH net 0/3] There are some bugfix for hibmcge ethernet driver Jacob Keller
2025-10-24 7:24 ` Jijie Shao [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-31 13:47 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=f99d878c-abf3-41ae-ae7f-b1db4f205561@huawei.com \
--to=shaojijie@huawei.com \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=huangdonghua3@h-partners.com \
--cc=jacob.e.keller@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kuba@kernel.org \
--cc=lantao5@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=shenjian15@huawei.com \
--cc=yangshuaisong@h-partners.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
all inboxes | Powered by JetHome®