From: patchwork-bot+netdevbpf@kernel.org
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, vigneshr@ti.com,
lokeshvutla@ti.com, edumazet@google.com
Subject: Re: [PATCH net-next 0/2] net: ethernet: ti: am65-cpsw: use napi_complete_done() in TX completion
Date: Fri, 06 Aug 2021 10:10:05 +0000 [thread overview]
Message-ID: <162824460547.4294.14719198165397613138.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210805225532.2667-1-grygorii.strashko@ti.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 6 Aug 2021 01:55:30 +0300 you wrote:
> hi
>
> The intention of this series is to fully enable hard irqs deferral feature
> (hrtimers based HW IRQ coalescing) from Eric Dumazet [1] for TI K3 CPSW driver
> by using napi_complete_done() in TX completion path, so the combination of
> parameters (/sys/class/net/ethX/):
> napi_defer_hard_irqs
> gro_flush_timeout
> can be used for hard irqs deferral.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: ti: am65-cpsw-nuss: fix RX IRQ state after .ndo_stop()
https://git.kernel.org/netdev/net-next/c/47bfc4d128de
- [net-next,2/2] net: ethernet: ti: am65-cpsw: use napi_complete_done() in TX completion
https://git.kernel.org/netdev/net-next/c/3bacbe04251b
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-08-06 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 22:55 [PATCH net-next 0/2] net: ethernet: ti: am65-cpsw: use napi_complete_done() in TX completion Grygorii Strashko
2021-08-05 22:55 ` [PATCH net-next 1/2] net: ti: am65-cpsw-nuss: fix RX IRQ state after .ndo_stop() Grygorii Strashko
2021-08-05 22:55 ` [PATCH net-next 2/2] net: ethernet: ti: am65-cpsw: use napi_complete_done() in TX completion Grygorii Strashko
2021-08-06 10:10 ` 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=162824460547.4294.14719198165397613138.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=netdev@vger.kernel.org \
--cc=vigneshr@ti.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