lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: 
 <174043623374.3631570.5317337904130972259.git-patchwork-notify@kernel.org>
Date: Mon, 24 Feb 2025 22:30:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
Cc: alexandre.torgue@...s.st.com, andrew+netdev@...n.ch, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 rmk+kernel@...linux.org.uk, chenhuacai@...nel.org, netdev@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2] net: stmmac: Correct usage of maximum queue
 number macros

Hello:

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

On Fri, 21 Feb 2025 14:18:18 +0900 you wrote:
> The maximum numbers of each Rx and Tx queues are defined by
> MTL_MAX_RX_QUEUES and MTL_MAX_TX_QUEUES respectively.
> 
> There are some places where Rx and Tx are used in reverse. There is no
> issue when the Tx and Rx macros have the same value, but should correct
> usage of macros for maximum queue number to keep consistency and prevent
> unexpected mistakes.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: stmmac: Correct usage of maximum queue number macros
    https://git.kernel.org/netdev/net-next/c/352bc4513ec3

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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ