From: patchwork-bot+netdevbpf@kernel.org
To: Brett Creeley <brett.creeley@amd.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
drivers@pensando.io, shannon.nelson@amd.com, allen.hubbe@amd.com
Subject: Re: [PATCH net-next] ionic: Don't overwrite the cyclecounter bitmask
Date: Wed, 12 Apr 2023 08:40:19 +0000 [thread overview]
Message-ID: <168128881913.3903.15231214701104787137.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230407184539.27559-1-brett.creeley@amd.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 7 Apr 2023 11:45:39 -0700 you wrote:
> The driver was incorrectly overwriting the cyclecounter bitmask,
> which was truncating it and not aligning to the hardware mask value.
> This isn't causing any issues, but it's wrong. Fix this by not
> constraining the cyclecounter/hardware mask.
>
> Luckily, this seems to cause no issues, which is why this change
> doesn't have a fixes tag and isn't being sent to net. However, if
> any transformations from time->cycles are needed in the future,
> this change will be needed.
>
> [...]
Here is the summary with links:
- [net-next] ionic: Don't overwrite the cyclecounter bitmask
https://git.kernel.org/netdev/net-next/c/be690daa224e
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-04-12 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 18:45 [PATCH net-next] ionic: Don't overwrite the cyclecounter bitmask Brett Creeley
2023-04-08 13:32 ` Simon Horman
2023-04-12 8: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=168128881913.3903.15231214701104787137.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=allen.hubbe@amd.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.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;
as well as URLs for NNTP newsgroup(s).