From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, xiaoliang.yang_1@nxp.com,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
UNGLinuxDriver@microchip.com, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com, michael@walle.cc,
vinicius.gomes@intel.com, fido_max@inbox.ru,
colin.foster@in-advantage.com, richard.pearn@nxp.com,
linux-kernel@vger.kernel.org, luto@kernel.org,
tglx@linutronix.de, vincenzo.frascino@arm.com
Subject: Re: [PATCH v2 net-next 0/4] Prevent permanently closed tc-taprio gates from blocking a Felix DSA switch port
Date: Fri, 01 Jul 2022 06:00:14 +0000 [thread overview]
Message-ID: <165665521464.30449.14354184109113080227.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220628145238.3247853-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Jun 2022 17:52:34 +0300 you wrote:
> v1->v2:
> - define PSEC_PER_NSEC in include/linux/time64.h rather than
> include/vdso/time64.h
> - add missing #include <linux/time.h> to users of PSEC_PER_NSEC
> - move the PSEC_PER_NSEC consolidation to the last patch
>
> Richie Pearn reports that if we install a tc-taprio schedule on a Felix
> switch port, and that schedule has at least one gate that never opens
> (for example TC0 below):
>
> [...]
Here is the summary with links:
- [v2,net-next,1/4] net: dsa: felix: keep reference on entire tc-taprio config
https://git.kernel.org/netdev/net-next/c/1c9017e44af2
- [v2,net-next,2/4] net: dsa: felix: keep QSYS_TAG_CONFIG_INIT_GATE_STATE(0xFF) out of rmw
https://git.kernel.org/netdev/net-next/c/d68a373bfbf4
- [v2,net-next,3/4] net: dsa: felix: drop oversized frames with tc-taprio instead of hanging the port
https://git.kernel.org/netdev/net-next/c/55a515b1f5a9
- [v2,net-next,4/4] time64.h: consolidate uses of PSEC_PER_NSEC
https://git.kernel.org/netdev/net-next/c/837ced3a1a5d
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:[~2022-07-01 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 14:52 [PATCH v2 net-next 0/4] Prevent permanently closed tc-taprio gates from blocking a Felix DSA switch port Vladimir Oltean
2022-06-28 14:52 ` [PATCH v2 net-next 1/4] net: dsa: felix: keep reference on entire tc-taprio config Vladimir Oltean
2022-06-28 14:52 ` [PATCH v2 net-next 2/4] net: dsa: felix: keep QSYS_TAG_CONFIG_INIT_GATE_STATE(0xFF) out of rmw Vladimir Oltean
2022-06-28 14:52 ` [PATCH v2 net-next 3/4] net: dsa: felix: drop oversized frames with tc-taprio instead of hanging the port Vladimir Oltean
2022-06-28 14:52 ` [PATCH v2 net-next 4/4] time64.h: consolidate uses of PSEC_PER_NSEC Vladimir Oltean
2022-06-28 15:31 ` Vincenzo Frascino
2022-07-01 6: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=165665521464.30449.14354184109113080227.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=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=fido_max@inbox.ru \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richard.pearn@nxp.com \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=vinicius.gomes@intel.com \
--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