[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <61CC2BC414934749BD9F5BF3D5D9404498748DAB@ORSMSX112.amr.corp.intel.com>
Date: Thu, 2 Jul 2020 21:26:54 +0000
From: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
To: Francesco Ruggeri <fruggeri@...sta.com>
CC: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
Jakub Kicinski <kuba@...nel.org>,
David Miller <davem@...emloft.net>,
open list <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: RE: [PATCH] igb: reinit_locked() should be called with rtnl_lock
> -----Original Message-----
> From: Francesco Ruggeri <fruggeri@...sta.com>
> Sent: Thursday, July 2, 2020 13:20
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@...el.com>
> Cc: Nguyen, Anthony L <anthony.l.nguyen@...el.com>; Jakub Kicinski
> <kuba@...nel.org>; David Miller <davem@...emloft.net>; open list <linux-
> kernel@...r.kernel.org>; netdev <netdev@...r.kernel.org>; intel-wired-
> lan@...ts.osuosl.org
> Subject: Re: [PATCH] igb: reinit_locked() should be called with rtnl_lock
>
> >
> > So will you be sending a v2 of your patch to include the second fix?
>
> Yes, I am working on it. Just to confirm, v2 should include both fixes, right?
Correct.
Powered by blists - more mailing lists