[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250122062713.09c9f8c9@kernel.org>
Date: Wed, 22 Jan 2025 06:27:13 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Michael Chan <michael.chan@...adcom.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
dan.carpenter@...aro.org, pavan.chebbi@...adcom.com, mchan@...adcom.com,
kuniyu@...zon.com, romieu@...zoreil.com
Subject: Re: [PATCH net-next 1/7] eth: tg3: fix calling napi_enable() in
atomic context
On Tue, 21 Jan 2025 23:41:53 -0800 Michael Chan wrote:
> One minor suggestion is to add the Sparse macros:
>
> __releases(tp->dev->lock)
> __acquires(tp->dev->lock)
>
> to tg3_restart_hw() since we already do the same thing there for tp->lock.
Does anyone actually use the sparse lock checking?
IIUC it's disabled by default, it's too noisy.
netdev_lock / netdev_unlock don't have the annotations.
Powered by blists - more mailing lists