From: patchwork-bot+netdevbpf@kernel.org
To: Fredrik Nyberg <fredrik.nyberg@volvocars.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, joalonsof@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH net] net: usb: ax88179_178a: fix rx frame length for non-last packets
Date: Wed, 07 Oct 2026 23:50:05 +0000 [thread overview]
Message-ID: <179141700528.3739009.13126482907868656699.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261002-ax88179-rx-len-v1-1-f01a2a295079@volvocars.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 02 Oct 2026 14:28:57 +0200 you wrote:
> From: Fredrik Nyberg <fredrik.nyberg@volvocars.com>
>
> Commit 4ce62d5b2f7a ("net: usb: ax88179_178a: stop lying about
> skb->truesize") replaced skb_clone() with a copy into a new skb for
> every packet of a bulk-in transfer except the last one. The copy skips
> the 2-byte IP alignment pseudo header but still copies pkt_len bytes,
> and pkt_len includes that header. Each of these frames is therefore
> delivered with two extra trailing bytes: the 0xeeee pseudo header of
> the next slot when the frame ends on an 8-byte boundary, or slot
> padding otherwise. The last packet is still trimmed to pkt_len - 2.
>
> [...]
Here is the summary with links:
- [net] net: usb: ax88179_178a: fix rx frame length for non-last packets
https://git.kernel.org/netdev/net/c/9b6c20f78847
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-10-07 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 12:28 [PATCH net] net: usb: ax88179_178a: fix rx frame length for non-last packets Fredrik Nyberg via B4 Relay
2026-10-07 14:31 ` Simon Horman
2026-10-07 23:44 ` Jakub Kicinski
2026-10-07 23:50 ` 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=179141700528.3739009.13126482907868656699.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=fredrik.nyberg@volvocars.com \
--cc=horms@kernel.org \
--cc=joalonsof@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/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