From: patchwork-bot+netdevbpf@kernel.org
To: Juhee Kang <claudiajkang@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
eric.dumazet@gmail.com, ennoerlangen@gmail.com,
george.mccollister@gmail.com, olteanv@gmail.com,
marco.wenzel@a-eberle.de
Subject: Re: [PATCH net-next] net: hsr: fix hsr build error when lockdep is not enabled
Date: Tue, 22 Feb 2022 05:00:10 +0000 [thread overview]
Message-ID: <164550601022.6244.4584908530321869685.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220220153250.5285-1-claudiajkang@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 20 Feb 2022 15:32:50 +0000 you wrote:
> In hsr, lockdep_is_held() is needed for rcu_dereference_bh_check().
> But if lockdep is not enabled, lockdep_is_held() causes a build error:
>
> ERROR: modpost: "lockdep_is_held" [net/hsr/hsr.ko] undefined!
>
> Thus, this patch solved by adding lockdep_hsr_is_held(). This helper
> function calls the lockdep_is_held() when lockdep is enabled, and returns 1
> if not defined.
>
> [...]
Here is the summary with links:
- [net-next] net: hsr: fix hsr build error when lockdep is not enabled
https://git.kernel.org/netdev/net-next/c/a0b92e0514bb
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-02-22 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 15:32 [PATCH net-next] net: hsr: fix hsr build error when lockdep is not enabled Juhee Kang
2022-02-22 4:47 ` Jakub Kicinski
2022-02-22 10:27 ` Juhee Kang
2022-02-22 5: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=164550601022.6244.4584908530321869685.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiajkang@gmail.com \
--cc=davem@davemloft.net \
--cc=ennoerlangen@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=kuba@kernel.org \
--cc=marco.wenzel@a-eberle.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.