[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN8PR12MB3266F0534CE20CE906AA3C06D30C0@BN8PR12MB3266.namprd12.prod.outlook.com>
Date: Wed, 22 Jan 2020 09:55:52 +0000
From: Jose Abreu <Jose.Abreu@...opsys.com>
To: Ong Boon Leong <boon.leong.ong@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: Tan Tee Min <tee.min.tan@...el.com>,
Voon Weifeng <weifeng.voon@...el.com>,
Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre TORGUE <alexandre.torgue@...com>,
"David S . Miller" <davem@...emloft.net>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
"Joao Pinto" <Joao.Pinto@...opsys.com>,
Arnd Bergmann <arnd@...db.de>,
"Alexandru Ardelean" <alexandru.ardelean@...log.com>,
"linux-stm32@...md-mailman.stormreply.com"
<linux-stm32@...md-mailman.stormreply.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH net v3 1/5] net: stmmac: Fix incorrect location to set
real_num_rx|tx_queues
From: Ong Boon Leong <boon.leong.ong@...el.com>
Date: Jan/22/2020, 09:09:32 (UTC+00:00)
> For driver open(), rtnl_lock is acquired by network stack but not in the
> resume(). Therefore, we introduce lock_acquired boolean to control when
> to use rtnl_lock|unlock() within stmmac_hw_setup().
Why not use rtnl_is_locked() instead of the boolean ?
---
Thanks,
Jose Miguel Abreu
Powered by blists - more mailing lists