From: Jakub Kicinski <kuba@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yibo Dong <dong100@mucse.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
gur.stavi@huawei.com, maddy@linux.ibm.com, mpe@ellerman.id.au,
danishanwar@ti.com, lee@trager.us, gongfan1@huawei.com,
lorenzo@kernel.org, geert+renesas@glider.be,
Parthiban.Veerasooran@microchip.com, lukas.bulwahn@redhat.com,
alexanderduyck@fb.com, richardcochran@gmail.com,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/5] net: rnpgbe: Add basic mbx_fw support
Date: Wed, 13 Aug 2025 14:32:05 -0700 [thread overview]
Message-ID: <20250813143205.1c0bfafa@kernel.org> (raw)
In-Reply-To: <CAMuHMdWpmt2q9tVm-3HV1h2=-7D6zEs_HnBe5gfYVgvfB=01hQ@mail.gmail.com>
On Wed, 13 Aug 2025 13:05:36 +0200 Geert Uytterhoeven wrote:
> Or use scoped_cond_guard(mutex_intr, ...) { ... }?
Hard no on that in networking.
next prev parent reply other threads:[~2025-08-13 21:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 9:39 [PATCH v3 0/5] Add driver for 1Gbe network chips from MUCSE Dong Yibo
2025-08-12 9:39 ` [PATCH v3 1/5] net: rnpgbe: Add build support for rnpgbe Dong Yibo
2025-08-12 15:37 ` Vadim Fedorenko
2025-08-13 6:18 ` Yibo Dong
2025-08-12 16:18 ` Anwar, Md Danish
2025-08-13 6:44 ` Yibo Dong
2025-08-13 7:51 ` MD Danish Anwar
2025-08-13 8:00 ` Yibo Dong
2025-08-12 9:39 ` [PATCH v3 2/5] net: rnpgbe: Add n500/n210 chip support Dong Yibo
2025-08-12 15:49 ` Vadim Fedorenko
2025-08-13 7:01 ` Yibo Dong
2025-08-12 16:25 ` Anwar, Md Danish
2025-08-13 7:07 ` Yibo Dong
2025-08-12 9:39 ` [PATCH v3 3/5] net: rnpgbe: Add basic mbx ops support Dong Yibo
2025-08-12 16:07 ` Vadim Fedorenko
2025-08-12 16:30 ` Anwar, Md Danish
2025-08-13 7:46 ` Yibo Dong
2025-08-14 23:55 ` Andrew Lunn
2025-08-15 1:31 ` Yibo Dong
2025-08-15 4:07 ` Andrew Lunn
2025-08-12 9:39 ` [PATCH v3 4/5] net: rnpgbe: Add basic mbx_fw support Dong Yibo
2025-08-12 16:14 ` Vadim Fedorenko
2025-08-13 8:12 ` Yibo Dong
2025-08-13 9:52 ` Yibo Dong
2025-08-13 11:05 ` Geert Uytterhoeven
2025-08-13 21:32 ` Jakub Kicinski [this message]
2025-08-13 13:33 ` Vadim Fedorenko
2025-08-14 1:53 ` Yibo Dong
2025-08-15 0:04 ` Andrew Lunn
2025-08-15 1:36 ` Yibo Dong
2025-08-13 8:20 ` MD Danish Anwar
2025-08-13 9:24 ` Yibo Dong
2025-08-12 9:39 ` [PATCH v3 5/5] net: rnpgbe: Add register_netdev Dong Yibo
2025-08-12 15:32 ` Vadim Fedorenko
2025-08-13 9:04 ` Yibo Dong
2025-08-13 12:50 ` Vadim Fedorenko
2025-08-14 1:52 ` Yibo Dong
2025-08-13 8:26 ` MD Danish Anwar
2025-08-13 9:49 ` Yibo Dong
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=20250813143205.1c0bfafa@kernel.org \
--to=kuba@kernel.org \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=dong100@mucse.com \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=gongfan1@huawei.com \
--cc=gur.stavi@huawei.com \
--cc=horms@kernel.org \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).