From: patchwork-bot+netdevbpf@kernel.org
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, pabeni@redhat.com,
ap420073@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxarm@openeuler.org
Subject: Re: [PATCH net] net: sched: fix lockdep_set_class() typo error for sch->seqlock
Date: Wed, 04 Aug 2021 09:10:05 +0000 [thread overview]
Message-ID: <162806820541.32022.5420198468163406896.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1627988301-55801-1-git-send-email-linyunsheng@huawei.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 3 Aug 2021 18:58:21 +0800 you wrote:
> According to comment in qdisc_alloc(), sch->seqlock's lockdep
> class key should be set to qdisc_tx_busylock, due to possible
> type error, sch->busylock's lockdep class key is set to
> qdisc_tx_busylock, which is duplicated because sch->busylock's
> lockdep class key is already set in qdisc_alloc().
>
> So fix it by replacing sch->busylock with sch->seqlock.
>
> [...]
Here is the summary with links:
- [net] net: sched: fix lockdep_set_class() typo error for sch->seqlock
https://git.kernel.org/netdev/net/c/06f5553e0f0c
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-04 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 10:58 [PATCH net] net: sched: fix lockdep_set_class() typo error for sch->seqlock Yunsheng Lin
2021-08-04 9:10 ` 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=162806820541.32022.5420198468163406896.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiyou.wangcong@gmail.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).