From: patchwork-bot+netdevbpf@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
jerinj@marvell.com, hkelam@marvell.com, sbhatta@marvell.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/5] octeontx2-af: Fix a potentially spurious error message
Date: Thu, 01 Dec 2022 04:50:16 +0000 [thread overview]
Message-ID: <166987021649.2850.15484096041241790130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5ce01c402f86412dc57884ff0994b63f0c5b3871.1669378798.git.christophe.jaillet@wanadoo.fr>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 25 Nov 2022 13:23:57 +0100 you wrote:
> When this error message is displayed, we know that the all the bits in the
> bitmap are set.
>
> So, bitmap_weight() will return the number of bits of the bitmap, which is
> 'table->tot_ids'.
>
> It is unlikely that a bit will be cleared between mutex_unlock() and
> dev_err(), but, in order to simplify the code and avoid this possibility,
> just take 'table->tot_ids'.
>
> [...]
Here is the summary with links:
- [1/5] octeontx2-af: Fix a potentially spurious error message
https://git.kernel.org/netdev/net-next/c/2450d7d93fd2
- [2/5] octeontx2-af: Slightly simplify rvu_npc_exact_init()
https://git.kernel.org/netdev/net-next/c/b6a0ecaee2e6
- [3/5] octeontx2-af: Use the bitmap API to allocate bitmaps
https://git.kernel.org/netdev/net-next/c/05a7b52ee5e4
- [4/5] octeontx2-af: Fix the size of memory allocated for the 'id_bmap' bitmap
https://git.kernel.org/netdev/net-next/c/6d135d9e2b00
- [5/5] octeontx2-af: Simplify a size computation in rvu_npc_exact_init()
https://git.kernel.org/netdev/net-next/c/450f06505396
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-12-01 4:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 12:23 [PATCH 0/5] octeontx2-af: Clean-up some bitmap related usage Christophe JAILLET
2022-11-25 12:23 ` [PATCH 1/5] octeontx2-af: Fix a potentially spurious error message Christophe JAILLET
2022-12-01 4:50 ` patchwork-bot+netdevbpf [this message]
2022-11-25 12:23 ` [PATCH 2/5] octeontx2-af: Slightly simplify rvu_npc_exact_init() Christophe JAILLET
2022-11-25 12:23 ` [PATCH 3/5] octeontx2-af: Use the bitmap API to allocate bitmaps Christophe JAILLET
2022-11-25 12:24 ` [PATCH 4/5] octeontx2-af: Fix the size of memory allocated for the 'id_bmap' bitmap Christophe JAILLET
2022-11-25 12:24 ` [PATCH 5/5] octeontx2-af: Simplify a size computation in rvu_npc_exact_init() Christophe JAILLET
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=166987021649.2850.15484096041241790130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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.