From: patchwork-bot+netdevbpf@kernel.org
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
ben.hutchings@essensium.com, linux-kernel@vger.kernel.org,
vigneshr@ti.com, linux-omap@vger.kernel.org, lokeshvutla@ti.com,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: ethernet: ti: cpsw: fix min eth packet size for non-switch use-cases
Date: Mon, 09 Aug 2021 09:20:05 +0000 [thread overview]
Message-ID: <162850080528.12236.16924791752972517567.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210805145511.12016-1-grygorii.strashko@ti.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 5 Aug 2021 17:55:11 +0300 you wrote:
> The CPSW switchdev driver inherited fix from commit 9421c9015047 ("net:
> ethernet: ti: cpsw: fix min eth packet size") which changes min TX packet
> size to 64bytes (VLAN_ETH_ZLEN, excluding ETH_FCS). It was done to fix HW
> packed drop issue when packets are sent from Host to the port with PVID and
> un-tagging enabled. Unfortunately this breaks some other non-switch
> specific use-cases, like:
> - [1] CPSW port as DSA CPU port with DSA-tag applied at the end of the
> packet
> - [2] Some industrial protocols, which expects min TX packet size 60Bytes
> (excluding FCS).
>
> [...]
Here is the summary with links:
- [net,v2] net: ethernet: ti: cpsw: fix min eth packet size for non-switch use-cases
https://git.kernel.org/netdev/net/c/acc68b8d2a11
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-08-09 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 14:55 [PATCH net v2] net: ethernet: ti: cpsw: fix min eth packet size for non-switch use-cases Grygorii Strashko
2021-08-05 18:43 ` Grygorii Strashko
2021-08-09 9:20 ` 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=162850080528.12236.16924791752972517567.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ben.hutchings@essensium.com \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vigneshr@ti.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).