All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: abin.joseph@amd.com, radhey.shyam.pandey@amd.com,
	michal.simek@amd.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org,
	darren.kenny@oracle.com
Subject: Re: [PATCH net] net: ll_temac: Fix missing tx_pending check in ethtools_set_ringparam()
Date: Fri, 11 Jul 2025 14:40:23 +0000	[thread overview]
Message-ID: <175224482399.2294782.1924457326744652237.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250710180621.2383000-1-alok.a.tiwari@oracle.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 10 Jul 2025 11:06:17 -0700 you wrote:
> The function ll_temac_ethtools_set_ringparam() incorrectly checked
> rx_pending twice, once correctly for RX and once mistakenly in place
> of tx_pending. This caused tx_pending to be left unchecked against
> TX_BD_NUM_MAX.
> As a result, invalid TX ring sizes may have been accepted or valid
> ones wrongly rejected based on the RX limit, leading to potential
> misconfiguration or unexpected results.
> 
> [...]

Here is the summary with links:
  - [net] net: ll_temac: Fix missing tx_pending check in ethtools_set_ringparam()
    https://git.kernel.org/netdev/net/c/e81750b4e382

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-07-11 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 18:06 [PATCH net] net: ll_temac: Fix missing tx_pending check in ethtools_set_ringparam() Alok Tiwari
2025-07-11 14:40 ` patchwork-bot+netdevbpf [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=175224482399.2294782.1924457326744652237.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=abin.joseph@amd.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=darren.kenny@oracle.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radhey.shyam.pandey@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.