From: patchwork-bot+netdevbpf@kernel.org
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: bryan.whitehead@microchip.com, davem@davemloft.net,
kuba@kernel.org, george.mccollister@gmail.com,
hkallweit1@gmail.com, andrew@lunn.ch,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v1] lan743x: fix ethernet frame cutoff issue
Date: Fri, 09 Apr 2021 20:00:37 +0000 [thread overview]
Message-ID: <161799843781.9153.1286906568340511297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210409003904.8957-1-TheSven73@gmail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 8 Apr 2021 20:39:04 -0400 you wrote:
> From: Sven Van Asbroeck <thesven73@gmail.com>
>
> The ethernet frame length is calculated incorrectly. Depending on
> the value of RX_HEAD_PADDING, this may result in ethernet frames
> that are too short (cut off at the end), or too long (garbage added
> to the end).
>
> [...]
Here is the summary with links:
- [net,v1] lan743x: fix ethernet frame cutoff issue
https://git.kernel.org/netdev/net/c/3bc41d6d2721
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-04-09 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 0:39 [PATCH net v1] lan743x: fix ethernet frame cutoff issue Sven Van Asbroeck
2021-04-09 1:02 ` Andrew Lunn
2021-04-09 1:13 ` Sven Van Asbroeck
2021-04-09 14:12 ` George McCollister
2021-04-09 14:38 ` Sven Van Asbroeck
2021-04-09 20:00 ` patchwork-bot+netdevbpf [this message]
2021-04-14 12:53 ` Julian Wiedmann
2021-04-14 13:19 ` Sven Van Asbroeck
2021-04-14 13:33 ` Julian Wiedmann
2021-04-14 13:40 ` Sven Van Asbroeck
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=161799843781.9153.1286906568340511297.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=george.mccollister@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thesven73@gmail.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).