LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mingming cao <mmc@linux.ibm.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, haren@linux.ibm.com,
	ricklind@linux.ibm.com, nnac123@linux.ibm.com,
	davemarq@linux.ibm.com, vaishnavi@linux.ibm.com,
	bjking1@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next v1 0/6] ibmvnic: honour flexible in-range MTU values
Date: Wed, 5 Aug 2026 22:28:28 -0700	[thread overview]
Message-ID: <22d2d33d-9118-4ccc-b5d0-0d41c2021eff@linux.ibm.com> (raw)
In-Reply-To: <20260805193832.645bdb30@kernel.org>


On 8/5/26 7:38 PM, Jakub Kicinski wrote:
> On Wed,  5 Aug 2026 15:43:55 -0700 Mingming Cao wrote:
>> Subject: [PATCH net-next v1 0/6] ibmvnic: honour flexible in-range MTU values
> Warning: drivers/net/ethernet/ibm/ibmvnic.c:1031 No description found for return value of 'rx_pool_entries'
>
>
> please DO NOT repost this until your previous series is reviewed and
> merged. Please read:
> https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
> There aren't supposed to be more than 15 outstanding patches form one
> person or company to one tree. We are flooded with AI-assisted code
> so reviews are slow. Your place in review queue depends on your
> credibility with the community so please help review other patches
> or just wait your turn.
Hi Jakub,

Thanks for the feedback.


Sorry for violating the outstanding patch limit. I wasn't aware of that 
rule, so thanks for pointing me to it.
I understand the review queue is already quite busy. I'll wait for the 
ibmveth MQ support series (v4, 14 patches) to progress through review 
before reposting this one.
In the meantime, I'm working through Sakashi's review comments on the 
ibmveth VQ v4 series.

For the ibmvnic MTU support series, I'll hold off on posting a v2 for 
now and will address the kernel-doc warning in the next revision.

Thanks again for the guidance.
Mingming




      reply	other threads:[~2026-08-06  5:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 22:43 [PATCH net-next v1 0/6] ibmvnic: honour flexible in-range MTU values Mingming Cao
2026-08-05 22:43 ` [PATCH net-next v1 1/6] ibmvnic: cap rx pool entries against the real buffer size Mingming Cao
2026-08-05 22:43 ` [PATCH net-next v1 2/6] ibmvnic: honour the requested mtu instead of reverting to a fallback Mingming Cao
2026-08-05 22:43 ` [PATCH net-next v1 3/6] ibmvnic: do not unmap long term buffers across a crq reconnect Mingming Cao
2026-08-05 22:43 ` [PATCH net-next v1 4/6] ibmvnic: allocate new buffer pools before releasing the old ones Mingming Cao
2026-08-05 22:44 ` [PATCH net-next v1 5/6] ibmvnic: allocate a new long term buffer before freeing the old one Mingming Cao
2026-08-05 22:44 ` [PATCH net-next v1 6/6] ibmvnic: change the mtu without a reset where the buffers allow it Mingming Cao
2026-08-06  2:38 ` [PATCH net-next v1 0/6] ibmvnic: honour flexible in-range MTU values Jakub Kicinski
2026-08-06  5:28   ` mingming cao [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=22d2d33d-9118-4ccc-b5d0-0d41c2021eff@linux.ibm.com \
    --to=mmc@linux.ibm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bjking1@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=davemarq@linux.ibm.com \
    --cc=edumazet@google.com \
    --cc=haren@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=nnac123@linux.ibm.com \
    --cc=pabeni@redhat.com \
    --cc=ricklind@linux.ibm.com \
    --cc=vaishnavi@linux.ibm.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