From: Jakub Kicinski <kuba@kernel.org>
To: <han.junyang@zte.com.cn>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<ran.ming@zte.com.cn>, <han.chengfei@zte.com.cn>,
<zhang.yanze@zte.com.cn>
Subject: Re: [PATCH net-next v1 0/3] dinghai: firmware handshake, MSI-X interrupts and async event queue
Date: Mon, 24 Aug 2026 10:00:05 -0700 [thread overview]
Message-ID: <20260824100005.06661b18@kernel.org> (raw)
In-Reply-To: <20260824033249934VsArgTPOU_qew94PPABbD@zte.com.cn>
On Mon, 24 Aug 2026 03:32:49 +0800 (CST) han.junyang@zte.com.cn wrote:
> Subject: [PATCH net-next v1 0/3] dinghai: firmware handshake, MSI-X interrupts and async event queue
## Form letter - net-next-closed
net-next pull request for v7.3 has already been merged, and therefore
the net-next tree is closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens after Aug 31st.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
pv-bot: closed
prev parent reply other threads:[~2026-08-24 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 19:32 han.junyang
2026-08-23 19:35 ` [PATCH net-next v1 1/3] dinghai: add firmware version check and RISC-V readiness polling han.junyang
2026-08-23 21:55 ` [PATCH net-next v1 1/3] dinghai: add firmware version check and? " Andrew Lunn
2026-08-24 17:59 ` Andrew Lunn
2026-08-23 19:37 ` [PATCH net-next v1 2/3] dinghai: add MSI-X interrupt pools han.junyang
2026-08-24 23:55 ` Andrew Lunn
2026-08-23 19:40 ` [PATCH net-next v1 3/3] dinghai: add async event queue for firmware notifications han.junyang
2026-08-24 17:00 ` Jakub Kicinski [this message]
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=20260824100005.06661b18@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=han.chengfei@zte.com.cn \
--cc=han.junyang@zte.com.cn \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ran.ming@zte.com.cn \
--cc=zhang.yanze@zte.com.cn \
/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®