From: Jijie Shao <shaojijie@huawei.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <shaojijie@huawei.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>, <horms@kernel.org>,
<shenjian15@huawei.com>, <liuyonglong@huawei.com>,
<chenhao418@huawei.com>, <lantao5@huawei.com>,
<huangdonghua3@h-partners.com>, <yangshuaisong@h-partners.com>,
<huangdengdui@h-partners.com>, <jonathan.cameron@huawei.com>,
<salil.mehta@huawei.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net 3/3] net: hns3: use user configure after hardware reset when using kernel PHY
Date: Fri, 19 Sep 2025 14:07:34 +0800 [thread overview]
Message-ID: <59d9add5-a4f5-4ee2-9fd8-a2ced4cbe0d4@huawei.com> (raw)
In-Reply-To: <5188066d-fcd2-41e7-bd8a-ae1dfbdd7731@lunn.ch>
on 2025/9/18 1:11, Andrew Lunn wrote:
> On Wed, Sep 17, 2025 at 08:29:54PM +0800, Jijie Shao wrote:
>> When a reset occurring
> Why would a reset occur? Is it the firmware crashing?
>
>> Consider the case that reset was happened consecutively.
> Does that mean the firmware crashed twice in quick succession?
>
> Andrew
Actually, We can trigger a reset by ethtool:
ethtool --reset ethx...
next prev parent reply other threads:[~2025-09-19 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 12:29 [PATCH net 0/3] There are some bugfix for the HNS3 ethernet driver Jijie Shao
2025-09-17 12:29 ` [PATCH net 1/3] net: hns3: fix loopback test of serdes and phy is failed if duplex is half Jijie Shao
2025-09-17 16:58 ` Andrew Lunn
2025-09-19 6:36 ` Jijie Shao
2025-09-17 12:29 ` [PATCH net 2/3] net: hns3: return error code when function fails Jijie Shao
2025-09-17 12:29 ` [PATCH net 3/3] net: hns3: use user configure after hardware reset when using kernel PHY Jijie Shao
2025-09-17 17:11 ` Andrew Lunn
2025-09-19 6:07 ` Jijie Shao [this message]
2025-09-19 12:20 ` Andrew Lunn
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=59d9add5-a4f5-4ee2-9fd8-a2ced4cbe0d4@huawei.com \
--to=shaojijie@huawei.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=huangdengdui@h-partners.com \
--cc=huangdonghua3@h-partners.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®