From: patchwork-bot+netdevbpf@kernel.org
To: Jacky Chou <jacky_chou@aspeedtech.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, u.kleine-koenig@pengutronix.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ftgmac100: Ensure tx descriptor updates are visible
Date: Mon, 26 Aug 2024 13:10:28 +0000 [thread overview]
Message-ID: <172467782825.7852.12721685155366652197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240822073006.817173-1-jacky_chou@aspeedtech.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 22 Aug 2024 15:30:06 +0800 you wrote:
> The driver must ensure TX descriptor updates are visible
> before updating TX pointer and TX clear pointer.
>
> This resolves TX hangs observed on AST2600 when running
> iperf3.
>
> Signed-off-by: Jacky Chou <jacky_chou@aspeedtech.com>
>
> [...]
Here is the summary with links:
- net: ftgmac100: Ensure tx descriptor updates are visible
https://git.kernel.org/netdev/net/c/4186c8d9e6af
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-26 13:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 7:30 [PATCH] net: ftgmac100: Ensure tx descriptor updates are visible Jacky Chou
2024-08-26 13:10 ` patchwork-bot+netdevbpf [this message]
2024-09-09 5:44 ` Joel Stanley
-- strict thread matches above, loose matches on Subject: below --
2020-10-20 22:06 Joel Stanley
2020-10-20 22:06 ` Joel Stanley
2020-10-21 0:00 ` Benjamin Herrenschmidt
2020-10-21 0:00 ` Benjamin Herrenschmidt
2020-10-21 3:37 ` Joel Stanley
2020-10-21 3:37 ` Joel Stanley
2020-10-21 8:18 ` David Laight
2020-10-21 8:18 ` David Laight
2020-10-22 7:37 ` Benjamin Herrenschmidt
2020-10-22 7:37 ` Benjamin Herrenschmidt
2020-10-21 12:40 ` Arnd Bergmann
2020-10-21 12:40 ` Arnd Bergmann
2020-10-22 6:35 ` Joel Stanley
2020-10-22 6:35 ` Joel Stanley
2020-10-22 7:41 ` Benjamin Herrenschmidt
2020-10-22 7:41 ` Benjamin Herrenschmidt
2020-10-28 4:47 ` Joel Stanley
2020-10-28 4:47 ` Joel Stanley
2020-10-28 10:51 ` Arnd Bergmann
2020-10-28 10:51 ` Arnd Bergmann
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=172467782825.7852.12721685155366652197.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacky_chou@aspeedtech.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.