From: patchwork-bot+netdevbpf@kernel.org
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: alexandre.torgue@foss.st.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, rmk+kernel@armlinux.org.uk,
chenhuacai@kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: stmmac: Correct usage of maximum queue number macros
Date: Mon, 24 Feb 2025 22:30:33 +0000 [thread overview]
Message-ID: <174043623374.3631570.5317337904130972259.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250221051818.4163678-1-hayashi.kunihiko@socionext.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2025-02-24 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 5:18 [PATCH net-next v2] net: stmmac: Correct usage of maximum queue number macros Kunihiko Hayashi
2025-02-24 22:30 ` 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=174043623374.3631570.5317337904130972259.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=chenhuacai@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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.