From: patchwork-bot+netdevbpf@kernel.org
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, sven@narfation.org,
penguin-kernel@i-love.sakura.ne.jp,
syzbot+c0b807de416427ff3dd1@syzkaller.appspotmail.com
Subject: Re: [PATCH 1/1] batman-adv: Avoid WARN_ON timing related checks
Date: Tue, 08 Jun 2021 19:20:03 +0000 [thread overview]
Message-ID: <162318000377.7737.11699354745969828257.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210608152947.30833-2-sw@simonwunderlich.de>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 8 Jun 2021 17:29:47 +0200 you wrote:
> From: Sven Eckelmann <sven@narfation.org>
>
> The soft/batadv interface for a queued OGM can be changed during the time
> the OGM was queued for transmission and when the OGM is actually
> transmitted by the worker.
>
> But WARN_ON must be used to denote kernel bugs and not to print simple
> warnings. A warning can simply be printed using pr_warn.
>
> [...]
Here is the summary with links:
- [1/1] batman-adv: Avoid WARN_ON timing related checks
https://git.kernel.org/netdev/net/c/9f460ae31c44
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-06-08 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 15:29 [PATCH 0/1] pull request for net: batman-adv 2021-06-08 Simon Wunderlich
2021-06-08 15:29 ` Simon Wunderlich
2021-06-08 15:29 ` [PATCH 1/1] batman-adv: Avoid WARN_ON timing related checks Simon Wunderlich
2021-06-08 19: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=162318000377.7737.11699354745969828257.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
--cc=syzbot+c0b807de416427ff3dd1@syzkaller.appspotmail.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.