From: Jakub Kicinski <kuba@kernel.org>
To: Justin Chen <justin.chen@broadcom.com>
Cc: netdev-bot+sinfo@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, edumazet@kernel.org, davem@davemloft.net,
andrew+netdev@lunn.ch, bcm-kernel-feedback-list@broadcom.com,
nb@tipi-net.de, florian.fainelli@broadcom.com, opendmb@gmail.com
Subject: Re: [PATCH net v2] net: bcmgenet: if UMAC was suspended in SW_RESET, restore it to SW_RESET
Date: Tue, 6 Oct 2026 15:44:07 -0700 [thread overview]
Message-ID: <20261006154407.64ecac6b@kernel.org> (raw)
In-Reply-To: <a1dc7c80-acef-479b-ad03-dc83164d77c2@broadcom.com>
On Tue, 6 Oct 2026 15:29:01 -0700 Justin Chen wrote:
> On 10/5/26 6:27 PM, Jakub Kicinski wrote:
> > On Fri, 2 Oct 2026 09:16:15 -0700 Justin Chen wrote:
> >> The issue was hit in production and I verified the sequence keeps the TX
> >> disabled in my standalone test. I tested on an internal development
> >> board with bcm77122, but should be reproducible on any genet HW that
> >> supports power management.
> >
> > I obviously meant that you should respond to all the fix info requests.
> > Not just this one in particular.
>
> Sorry Jakub, I am not understanding what you are asking for. I believe I
> answered the questions above? Or am I missing something else?
I mean other threads, immediate example:
https://lore.kernel.org/all/20260929203400.1588868-1-justin.chen@broadcom.com/
next prev parent reply other threads:[~2026-10-06 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 23:06 [PATCH net v2] net: bcmgenet: if UMAC was suspended in SW_RESET, restore it to SW_RESET Justin Chen
2026-09-30 23:08 ` netdev-bot+sinfo
2026-10-02 1:41 ` Jakub Kicinski
2026-10-02 16:16 ` Justin Chen
2026-10-06 1:27 ` Jakub Kicinski
2026-10-06 22:29 ` Justin Chen
2026-10-06 22:44 ` Jakub Kicinski [this message]
2026-10-06 23:05 ` Justin Chen
2026-10-07 1:38 ` Jakub Kicinski
2026-10-07 1:50 ` patchwork-bot+netdevbpf
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=20261006154407.64ecac6b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=nb@tipi-net.de \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.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