From: Jakub Kicinski <kuba@kernel.org>
To: Xin Tian <tianx@yunsilicon.com>
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, leon@kernel.org, andrew+netdev@lunn.ch,
pabeni@redhat.com, edumazet@google.com, davem@davemloft.net,
jeff.johnson@oss.qualcomm.com, przemyslaw.kitszel@intel.com,
weihg@yunsilicon.com, wanry@yunsilicon.com, jacky@yunsilicon.com,
parthiban.veerasooran@microchip.com, masahiroy@kernel.org,
kalesh-anakkur.purayil@broadcom.com, geert+renesas@glider.be,
geert@linux-m68k.org
Subject: Re: [PATCH net-next v12 00/14] xsc: ADD Yunsilicon XSC Ethernet Driver
Date: Fri, 6 Jun 2025 06:31:20 -0700 [thread overview]
Message-ID: <20250606063120.72c429ad@kernel.org> (raw)
In-Reply-To: <20250606131342.GG120308@horms.kernel.org>
On Fri, 6 Jun 2025 14:13:42 +0100 Simon Horman wrote:
> Hi Xin Tian,
>
> Thanks for the updates. Unfortunately the timing of this submission is
> not ideal.
>
> ## Form letter - net-next-closed
>
> The merge window for v6.16 has begun and therefore net-next is closed
> for new drivers, features, code refactoring and optimizations. We are
> currently accepting bug fixes only.
>
> Please repost when net-next reopens after June 8th.
>
> RFC patches sent for review only are obviously welcome at any time.
Yes.
Please read
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
before you send any more code out.
--
pv-bot: 24h
next prev parent reply other threads:[~2025-06-06 13:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 10:02 [PATCH net-next v12 00/14] xsc: ADD Yunsilicon XSC Ethernet Driver Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 01/14] xsc: Add xsc driver basic framework Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 02/14] xsc: Enable command queue Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 03/14] xsc: Add hardware setup APIs Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 04/14] xsc: Add qp and cq management Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 05/14] xsc: Add eq and alloc Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 06/14] xsc: Init pci irq Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 07/14] xsc: Init auxiliary device Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 08/14] xsc: Add ethernet interface Xin Tian
2025-06-06 10:01 ` [PATCH net-next v12 09/14] xsc: Init net device Xin Tian
2025-06-06 10:02 ` [PATCH net-next v12 10/14] xsc: Add eth needed qp and cq apis Xin Tian
2025-06-06 10:02 ` [PATCH net-next v12 11/14] xsc: ndo_open and ndo_stop Xin Tian
2025-06-06 10:02 ` [PATCH net-next v12 12/14] xsc: Add ndo_start_xmit Xin Tian
2025-06-06 10:02 ` [PATCH net-next v12 13/14] xsc: Add eth reception data path Xin Tian
2025-06-06 10:02 ` [PATCH net-next v12 14/14] xsc: add ndo_get_stats64 Xin Tian
2025-06-06 13:13 ` [PATCH net-next v12 00/14] xsc: ADD Yunsilicon XSC Ethernet Driver Simon Horman
2025-06-06 13:31 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-08 8:59 Xin Tian
2025-07-03 7:54 Xin Tian
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=20250606063120.72c429ad@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@kernel.org \
--cc=jacky@yunsilicon.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parthiban.veerasooran@microchip.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tianx@yunsilicon.com \
--cc=wanry@yunsilicon.com \
--cc=weihg@yunsilicon.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