From: MD Danish Anwar <danishanwar@ti.com>
To: Yibo Dong <dong100@mucse.com>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>, <corbet@lwn.net>, <gur.stavi@huawei.com>,
<maddy@linux.ibm.com>, <mpe@ellerman.id.au>, <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>, <kees@kernel.org>,
<gustavoars@kernel.org>, <rdunlap@infradead.org>,
<vadim.fedorenko@linux.dev>, <netdev@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCH net-next v9 0/5] Add driver for 1Gbe network chips from MUCSE
Date: Thu, 28 Aug 2025 12:17:54 +0530 [thread overview]
Message-ID: <37a7ce7d-f34b-4734-8c05-722f6d369193@ti.com> (raw)
In-Reply-To: <BC262E8E0C675110+20250828053659.GA645649@nic-Precision-5820-Tower>
On 28/08/25 11:06 am, Yibo Dong wrote:
> On Thu, Aug 28, 2025 at 10:52:21AM +0530, MD Danish Anwar wrote:
>> Hi Dong Yibo,
>>
>> On 28/08/25 8:25 am, Dong Yibo wrote:
>>> Hi maintainers,
>>>
>>> This patch series is v9 to introduce support for MUCSE N500/N210 1Gbps
>>> Ethernet controllers. I divide codes into multiple series, this is the
>>> first one which only register netdev without true tx/rx functions.
>>>
>>> Changelog:
>>> v8 -> v9:
>>> 1. update function description format '@return' to 'Return'
>>> 2. update 'negative on failure' to 'negative errno on failure'
>>>
>>> links:
>>> v8: https://lore.kernel.org/netdev/20250827034509.501980-1-dong100@mucse.com/
>>> v7: https://lore.kernel.org/netdev/20250822023453.1910972-1-dong100@mucse.com
>>> v6: https://lore.kernel.org/netdev/20250820092154.1643120-1-dong100@mucse.com/
>>> v5: https://lore.kernel.org/netdev/20250818112856.1446278-1-dong100@mucse.com/
>>> v4: https://lore.kernel.org/netdev/20250814073855.1060601-1-dong100@mucse.com/
>>> v3: https://lore.kernel.org/netdev/20250812093937.882045-1-dong100@mucse.com/
>>> v2: https://lore.kernel.org/netdev/20250721113238.18615-1-dong100@mucse.com/
>>> v1: https://lore.kernel.org/netdev/20250703014859.210110-1-dong100@mucse.com/
>>
>> Please wait for at least 24 hours before posting a new version. You
>> posted v8 yesterday and most folks won't have noticed v8 by now or they
>> maybe looking to give comments on v8. But before they could do that you
>> posted v9.
>>
>> Keep good amount of gaps between the series so that more folks can look
>> at it. 24 hours is the minimum.
>>
>> --
>> Thanks and Regards,
>> Danish
>>
>>
>
> Got it, I found the v8 pathes state in websit:
> https://patchwork.kernel.org/project/netdevbpf/list/
> It is 'Changes Requested'.
> I mistakenly thought that a new version needed to be sent. I will wait
That's correct. 'Changes Requested' means that version will no longer be
accepted and you have to send a newer one. But that doesn't mean you
have to send it immediately.
https://www.kernel.org/doc/html/v6.1/process/maintainer-netdev.html#i-have-received-review-feedback-when-should-i-post-a-revised-version-of-the-patches
> more time in the next time.
>
> Thanks for you feedback.
--
Thanks and Regards,
Danish
next prev parent reply other threads:[~2025-08-28 6:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 2:55 [PATCH net-next v9 0/5] Add driver for 1Gbe network chips from MUCSE Dong Yibo
2025-08-28 2:55 ` [PATCH net-next v9 1/5] net: rnpgbe: Add build support for rnpgbe Dong Yibo
2025-08-28 12:51 ` Andrew Lunn
2025-09-01 8:20 ` Yibo Dong
2025-09-01 9:58 ` Vadim Fedorenko
2025-09-02 1:31 ` Yibo Dong
2025-08-28 2:55 ` [PATCH net-next v9 2/5] net: rnpgbe: Add n500/n210 chip support Dong Yibo
2025-08-28 2:55 ` [PATCH net-next v9 3/5] net: rnpgbe: Add basic mbx ops support Dong Yibo
2025-08-28 2:55 ` [PATCH net-next v9 4/5] net: rnpgbe: Add basic mbx_fw support Dong Yibo
2025-08-28 13:09 ` Andrew Lunn
2025-08-29 2:12 ` Yibo Dong
2025-08-29 19:48 ` Andrew Lunn
2025-09-01 2:08 ` Yibo Dong
2025-09-01 7:27 ` Yibo Dong
2025-09-03 0:54 ` Andrew Lunn
2025-08-28 2:55 ` [PATCH net-next v9 5/5] net: rnpgbe: Add register_netdev Dong Yibo
2025-08-28 13:20 ` Andrew Lunn
2025-08-29 2:36 ` Yibo Dong
2025-08-29 19:51 ` Andrew Lunn
2025-09-01 2:18 ` Yibo Dong
2025-08-28 5:22 ` [PATCH net-next v9 0/5] Add driver for 1Gbe network chips from MUCSE MD Danish Anwar
2025-08-28 5:36 ` Yibo Dong
2025-08-28 6:47 ` MD Danish Anwar [this message]
2025-08-28 12:57 ` Andrew Lunn
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=37a7ce7d-f34b-4734-8c05-722f6d369193@ti.com \
--to=danishanwar@ti.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dong100@mucse.com \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=gongfan1@huawei.com \
--cc=gur.stavi@huawei.com \
--cc=gustavoars@kernel.org \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@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=rdunlap@infradead.org \
--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).