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 18:38:05 -0700 [thread overview]
Message-ID: <20261006183805.125a09fa@kernel.org> (raw)
In-Reply-To: <61e7e89a-c04f-4700-8387-5cbe776460ba@broadcom.com>
On Tue, 6 Oct 2026 16:05:48 -0700 Justin Chen wrote:
> >> 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/
>
> Hmmmm. Looks like those missing info emails didn't hit my inbox. They
> were sent as I can see them on kernel lore... Let me see what happened
> there. Florian submitted more patches, but these should be the only two
> inflight from me. But yes, I will answer on the bcmasp patch as well.
Thanks. I wonder if it's something about Broadcom email filters or we're
running afoul of gmail(?) with the rate of these automatic requests :(
next prev parent reply other threads:[~2026-10-07 1:38 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
2026-10-06 23:05 ` Justin Chen
2026-10-07 1:38 ` Jakub Kicinski [this message]
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=20261006183805.125a09fa@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 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.