From: patchwork-bot+netdevbpf@kernel.org
To: Michael Walle <michael@walle.cc>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
vladimir.oltean@nxp.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
davem@davemloft.net, kuba@kernel.org, xiaoliang.yang_1@nxp.com
Subject: Re: [PATCH net] net: dsa: felix: re-enable TAS guard band mode
Date: Mon, 10 May 2021 21:50:10 +0000 [thread overview]
Message-ID: <162068341014.4733.5616214407177373815.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210510110708.11504-1-michael@walle.cc>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 10 May 2021 13:07:08 +0200 you wrote:
> Commit 316bcffe4479 ("net: dsa: felix: disable always guard band bit for
> TAS config") disabled the guard band and broke 802.3Qbv compliance.
>
> There are two issues here:
> (1) Without the guard band the end of the scheduling window could be
> overrun by a frame in transit.
> (2) Frames that don't fit into a configured window will still be sent.
>
> [...]
Here is the summary with links:
- [net] net: dsa: felix: re-enable TAS guard band mode
https://git.kernel.org/netdev/net/c/297c4de6f780
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-05-10 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 11:07 [PATCH net] net: dsa: felix: re-enable TAS guard band mode Michael Walle
2021-05-10 12:23 ` Vladimir Oltean
2021-05-10 21: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=162068341014.4733.5616214407177373815.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.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