From: patchwork-bot+netdevbpf@kernel.org
To: Matthias-Christian Ott <ott@mirix.org>
Cc: petkan@nucleusys.com, linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] net: usb: pegasus: Do not drop long Ethernet frames
Date: Mon, 27 Dec 2021 15:00:10 +0000 [thread overview]
Message-ID: <164061721023.30887.10543849248134029481.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211226221208.2583-1-ott@mirix.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 26 Dec 2021 23:12:08 +0100 you wrote:
> The D-Link DSB-650TX (2001:4002) is unable to receive Ethernet frames
> that are longer than 1518 octets, for example, Ethernet frames that
> contain 802.1Q VLAN tags.
>
> The frames are sent to the pegasus driver via USB but the driver
> discards them because they have the Long_pkt field set to 1 in the
> received status report. The function read_bulk_callback of the pegasus
> driver treats such received "packets" (in the terminology of the
> hardware) as errors but the field simply does just indicate that the
> Ethernet frame (MAC destination to FCS) is longer than 1518 octets.
>
> [...]
Here is the summary with links:
- [net,v2] net: usb: pegasus: Do not drop long Ethernet frames
https://git.kernel.org/netdev/net/c/ca506fca461b
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:[~2021-12-27 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 22:12 [PATCH net v2] net: usb: pegasus: Do not drop long Ethernet frames Matthias-Christian Ott
2021-12-26 22:35 ` Andrew Lunn
2021-12-27 11:11 ` Petko Manolov
2022-01-02 14:16 ` Matthias-Christian Ott
2022-01-02 14:19 ` Matthias-Christian Ott
2021-12-27 15: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=164061721023.30887.10543849248134029481.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ott@mirix.org \
--cc=petkan@nucleusys.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).