From: patchwork-bot+netdevbpf@kernel.org
To: Yannick Vignon <yannick.vignon@oss.nxp.com>
Cc: sebastien.laveze@oss.npx.com, vinicius.gomes@intel.com,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
qiangqing.zhang@nxp.com, olteanv@gmail.com,
xiaoliang.yang_1@nxp.com, yannick.vignon@nxp.com
Subject: Re: [PATCH net] net/sched: taprio: Fix init procedure
Date: Mon, 02 Aug 2021 10:50:05 +0000 [thread overview]
Message-ID: <162790140532.10250.7097847427032850126.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210730165321.1179952-1-yannick.vignon@oss.nxp.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 30 Jul 2021 18:53:21 +0200 you wrote:
> From: Yannick Vignon <yannick.vignon@nxp.com>
>
> Commit 13511704f8d759 ("net: taprio offload: enforce qdisc to netdev queue mapping")
> resulted in duplicate entries in the qdisc hash.
> While this did not impact the overall operation of the qdisc and taprio
> code paths, it did result in an infinite loop when dumping the qdisc
> properties, at least on one target (NXP LS1028 ARDB).
> Removing the duplicate call to qdisc_hash_add() solves the problem.
>
> [...]
Here is the summary with links:
- [net] net/sched: taprio: Fix init procedure
https://git.kernel.org/netdev/net/c/ebca25ead071
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-02 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 16:53 [PATCH net] net/sched: taprio: Fix init procedure Yannick Vignon
2021-08-02 10: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=162790140532.10250.7097847427032850126.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=qiangqing.zhang@nxp.com \
--cc=sebastien.laveze@oss.npx.com \
--cc=vinicius.gomes@intel.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yannick.vignon@nxp.com \
--cc=yannick.vignon@oss.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;
as well as URLs for NNTP newsgroup(s).