From: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
To: Francesco Ruggeri <fruggeri@arista.com>
Cc: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
open list <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: RE: [PATCH] igb: reinit_locked() should be called with rtnl_lock
Date: Thu, 2 Jul 2020 21:26:54 +0000 [thread overview]
Message-ID: <61CC2BC414934749BD9F5BF3D5D9404498748DAB@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <CA+HUmGi6D8Ci5fk7vyengJN4qOEH6zz18Kw6B9Us-Kav-78oAg@mail.gmail.com>
> -----Original Message-----
> From: Francesco Ruggeri <fruggeri@arista.com>
> Sent: Thursday, July 2, 2020 13:20
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@intel.com>
> Cc: Nguyen, Anthony L <anthony.l.nguyen@intel.com>; Jakub Kicinski
> <kuba@kernel.org>; David Miller <davem@davemloft.net>; open list <linux-
> kernel@vger.kernel.org>; netdev <netdev@vger.kernel.org>; intel-wired-
> lan@lists.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.
prev parent reply other threads:[~2020-07-02 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 21:18 [PATCH] igb: reinit_locked() should be called with rtnl_lock Francesco Ruggeri
2020-06-30 0:16 ` Jakub Kicinski
2020-06-30 4:50 ` Francesco Ruggeri
2020-07-01 1:37 ` Kirsher, Jeffrey T
2020-07-02 19:35 ` Francesco Ruggeri
2020-07-02 20:05 ` Kirsher, Jeffrey T
2020-07-02 20:20 ` Francesco Ruggeri
2020-07-02 21:26 ` Kirsher, Jeffrey T [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61CC2BC414934749BD9F5BF3D5D9404498748DAB@ORSMSX112.amr.corp.intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=fruggeri@arista.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).