From: patchwork-bot+netdevbpf@kernel.org
To: Ronald Wahl <rwahl@gmx.de>
Cc: ronald.wahl@raritan.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
ben.dooks@codethink.co.uk, Tristram.Ha@microchip.com,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: ks8851: Fix TX stall caused by TX buffer overrun
Date: Tue, 19 Dec 2023 11:00:23 +0000 [thread overview]
Message-ID: <170298362378.20843.3373461129605286844.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231214181112.76052-1-rwahl@gmx.de>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 14 Dec 2023 19:11:12 +0100 you wrote:
> From: Ronald Wahl <ronald.wahl@raritan.com>
>
> There is a bug in the ks8851 Ethernet driver that more data is written
> to the hardware TX buffer than actually available. This is caused by
> wrong accounting of the free TX buffer space.
>
> The driver maintains a tx_space variable that represents the TX buffer
> space that is deemed to be free. The ks8851_start_xmit_spi() function
> adds an SKB to a queue if tx_space is large enough and reduces tx_space
> by the amount of buffer space it will later need in the TX buffer and
> then schedules a work item. If there is not enough space then the TX
> queue is stopped.
>
> [...]
Here is the summary with links:
- [net,v3] net: ks8851: Fix TX stall caused by TX buffer overrun
https://git.kernel.org/netdev/net/c/3dc5d4454545
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:[~2023-12-19 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 18:11 [PATCH net v3] net: ks8851: Fix TX stall caused by TX buffer overrun Ronald Wahl
2023-12-17 12:53 ` Simon Horman
2023-12-19 11:00 ` 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=170298362378.20843.3373461129605286844.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ronald.wahl@raritan.com \
--cc=rwahl@gmx.de \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).