From: patchwork-bot+netdevbpf@kernel.org
To: Alex Pakhunov <alexey.pakhunov@spacex.com>
Cc: mchan@broadcom.com, vincent.wong2@spacex.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
siva.kallam@broadcom.com, prashant@broadcom.com
Subject: Re: [PATCH v4 1/2] tg3: Move the [rt]x_dropped counters to tg3_napi
Date: Wed, 15 Nov 2023 04:00:25 +0000 [thread overview]
Message-ID: <170002082585.14036.6726245489238150125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231113182350.37472-1-alexey.pakhunov@spacex.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 13 Nov 2023 10:23:49 -0800 you wrote:
> From: Alex Pakhunov <alexey.pakhunov@spacex.com>
>
> This change moves [rt]x_dropped counters to tg3_napi so that they can be
> updated by a single writer, race-free.
>
> Signed-off-by: Alex Pakhunov <alexey.pakhunov@spacex.com>
> Signed-off-by: Vincent Wong <vincent.wong2@spacex.com>
>
> [...]
Here is the summary with links:
- [v4,1/2] tg3: Move the [rt]x_dropped counters to tg3_napi
https://git.kernel.org/netdev/net/c/907d1bdb8b2c
- [v4,2/2] tg3: Increment tx_dropped in tg3_tso_bug()
https://git.kernel.org/netdev/net/c/17dd5efe5f36
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-11-15 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 18:23 [PATCH v4 1/2] tg3: Move the [rt]x_dropped counters to tg3_napi alexey.pakhunov
2023-11-13 18:23 ` [PATCH v4 2/2] tg3: Increment tx_dropped in tg3_tso_bug() alexey.pakhunov
2023-11-14 10:06 ` Pavan Chebbi
2023-11-13 22:38 ` [PATCH v4 1/2] tg3: Move the [rt]x_dropped counters to tg3_napi Jakub Kicinski
2023-11-13 23:19 ` Michael Chan
2023-11-15 4: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=170002082585.14036.6726245489238150125.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexey.pakhunov@spacex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.com \
--cc=siva.kallam@broadcom.com \
--cc=vincent.wong2@spacex.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