From: patchwork-bot+netdevbpf@kernel.org
To: Daniil Iskhakov <dish@amicon.ru>
Cc: shenjian15@huawei.com, ade@amicon.ru, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rrv@amicon.ru,
lvc-project@linuxtesting.org
Subject: Re: [PATCH net-next v2] net: hns: use u32 for register offset in RCB TX coalescing
Date: Fri, 24 Jul 2026 22:40:06 +0000 [thread overview]
Message-ID: <178493280614.3338677.8807103639653876808.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715125856.19346-1-dish@amicon.ru>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 15 Jul 2026 15:58:48 +0300 you wrote:
> From: Daniil Agalakov <ade@amicon.ru>
>
> In both hns_rcb_get_tx_coalesced_frames() and
> hns_rcb_set_tx_coalesced_frames(), the local variable reg holds a
> register offset passed to dsaf_read_dev() or dsaf_write_dev().
>
> Register offsets on this hardware are 32-bit values. Use u32 for reg
> to match the register access interfaces and avoid implying that
> 64-bit offsets are supported.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: hns: use u32 for register offset in RCB TX coalescing
https://git.kernel.org/netdev/net-next/c/bf8cdde4ef35
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:[~2026-07-24 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 12:58 [PATCH net-next v2] net: hns: use u32 for register offset in RCB TX coalescing Daniil Iskhakov
2026-07-24 22: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=178493280614.3338677.8807103639653876808.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ade@amicon.ru \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dish@amicon.ru \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rrv@amicon.ru \
--cc=shenjian15@huawei.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