[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<CH2PR12MB389598B6D2C1EFA43F7B8936D73EA@CH2PR12MB3895.namprd12.prod.outlook.com>
Date: Thu, 20 Jul 2023 21:11:53 +0000
From: Asmaa Mnebhi <asmaa@...dia.com>
To: "davem@...emloft.net" <davem@...emloft.net>, "edumazet@...gle.com"
<edumazet@...gle.com>, "kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"sridhar.samudrala@...el.com" <sridhar.samudrala@...el.com>,
"maciej.fijalkowski@...el.com" <maciej.fijalkowski@...el.com>,
"olteanv@...il.com" <olteanv@...il.com>, David Thompson
<davthompson@...dia.com>
Subject: RE: [PATCH net v3 1/1] mlxbf_gige: Fix kernel panic at shutdown
> .probe = mlxbf_gige_probe,
> .remove = mlxbf_gige_remove,
> - .shutdown = mlxbf_gige_shutdown,
> + .shutdown = mlxbf_gige_remove,
Actually, apologies for this commit in response to Sridhar's comment on v2. This will not work. Mlxbf_gige_remove() returns void while ".shutdown" expects to return an int.
Please advise on how to proceed. Should I send a v4 with the same patch as v2?
Powered by blists - more mailing lists