[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166987021649.2850.15484096041241790130.git-patchwork-notify@kernel.org>
Date: Thu, 01 Dec 2022 04:50:16 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: sgoutham@...vell.com, lcherian@...vell.com, gakula@...vell.com,
jerinj@...vell.com, hkelam@...vell.com, sbhatta@...vell.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 1/5] octeontx2-af: Fix a potentially spurious error message
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.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
Powered by blists - more mailing lists