From: patchwork-bot+netdevbpf@kernel.org
To: Pengpeng Hou <hppiscas@163.com>
Cc: shenjian15@huawei.com, shaojijie@huawei.com,
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, xiaojiangfeng@huawei.com,
horms@kernel.org
Subject: Re: [PATCH net v2] net: hip04: use 16-bit byte order for HI13X1 TX fields
Date: Tue, 22 Sep 2026 00:40:10 +0000 [thread overview]
Message-ID: <179003761088.3308999.15696540056719264003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260920033641.13590-1-hppiscas@163.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 20 Sep 2026 11:36:41 +0800 you wrote:
> The HI13X1 TX descriptor stores send_size and data_offset in 16-bit
> fields, unlike the 32-bit send_size field in the other descriptor
> layout. The transmit path nevertheless converts both HI13X1 fields with
> cpu_to_be32() before assigning them to u16 members.
>
> On a little-endian CPU, the conversion moves these small values into the
> upper half of the 32-bit result and the assignment discards that half.
> The descriptor consequently loses the packet size and cache-line offset.
>
> [...]
Here is the summary with links:
- [net,v2] net: hip04: use 16-bit byte order for HI13X1 TX fields
https://git.kernel.org/netdev/net-next/c/114bd09838ac
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-09-22 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 3:36 [PATCH net v2] net: hip04: use 16-bit byte order for HI13X1 TX fields Pengpeng Hou
2026-09-22 0: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=179003761088.3308999.15696540056719264003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hppiscas@163.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=xiaojiangfeng@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