From: patchwork-bot+netdevbpf@kernel.org
To: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, vladimir.oltean@nxp.com,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
UNGLinuxDriver@microchip.com, andrew@lunn.ch,
f.fainelli@gmail.com, michael@walle.cc,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] net: dsa: felix: ignore pending status of TAS module when it's disabled
Date: Wed, 11 Sep 2024 23:20:37 +0000 [thread overview]
Message-ID: <172609683781.1105624.8461423176901679362.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240906093550.29985-1-xiaoliang.yang_1@nxp.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 6 Sep 2024 17:35:50 +0800 you wrote:
> The TAS module could not be configured when it's running in pending
> status. We need disable the module and configure it again. However, the
> pending status is not cleared after the module disabled. TC taprio set
> will always return busy even it's disabled.
>
> For example, a user uses tc-taprio to configure Qbv and a future
> basetime. The TAS module will run in a pending status. There is no way
> to reconfigure Qbv, it always returns busy.
>
> [...]
Here is the summary with links:
- [v2,net] net: dsa: felix: ignore pending status of TAS module when it's disabled
https://git.kernel.org/netdev/net/c/70654f4c212e
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:[~2024-09-11 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 9:35 [PATCH v2 net] net: dsa: felix: ignore pending status of TAS module when it's disabled Xiaoliang Yang
2024-09-11 23: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=172609683781.1105624.8461423176901679362.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=pabeni@redhat.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