From: patchwork-bot+netdevbpf@kernel.org
To: Ong Boon Leong <boon.leong.ong@intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/1] net: stmmac: add per-q coalesce support
Date: Wed, 17 Mar 2021 21:40:07 +0000 [thread overview]
Message-ID: <161601720759.5355.17806697288501319323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210317010123.6304-1-boon.leong.ong@intel.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 17 Mar 2021 09:01:22 +0800 you wrote:
> Hi,
>
> This patch adds per-queue RX & TX coalesce control so that user can
> adjust the RX & TX interrupt moderation per queue. This is beneficial for
> mixed criticality control (according to VLAN priority) by user application.
>
> The v2 patch has been tested (with added negative tests) and results from the
> output of the ethtool looks correct.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/1] net: stmmac: add per-queue TX & RX coalesce ethtool support
https://git.kernel.org/netdev/net-next/c/db2f2842e6f5
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:[~2021-03-17 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 1:01 Ong Boon Leong
2021-03-17 1:01 ` [PATCH net-next v2 1/1] net: stmmac: add per-queue TX & RX coalesce ethtool support Ong Boon Leong
2021-03-17 20:55 ` Jakub Kicinski
2021-03-17 21: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=161601720759.5355.17806697288501319323.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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
all inboxes | Powered by JetHome®