From: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
To: "kuba@kernel.org" <kuba@kernel.org>
Cc: "nhorman@redhat.com" <nhorman@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"sassmann@redhat.com" <sassmann@redhat.com>
Subject: Re: [net 0/2][pull request] Intel Wired LAN Driver Updates 2020-07-30
Date: Fri, 31 Jul 2020 15:33:53 +0000 [thread overview]
Message-ID: <2e85c879b30f39cfb1ce3fab11cd7178179d51fe.camel@intel.com> (raw)
In-Reply-To: <20200730162703.277cc07b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Thu, 2020-07-30 at 16:27 -0700, Jakub Kicinski wrote:
> On Thu, 30 Jul 2020 10:09:36 -0700 Tony Nguyen wrote:
> > This series contains updates to the e1000e and igb drivers.
> >
> > Aaron Ma allows PHY initialization to continue if ULP disable
> > failed for
> > e1000e.
> >
> > Francesco Ruggeri fixes race conditions in igb reset that could
> > cause panics.
>
> Reviewed-by: Jakub Kicinski <kuba@kernel.org>
>
> In the future please try to add Fixes tags on all net submissions
> (patch 2).
Will do.
> Also - are similar fixes for other Intel drivers in the
> works?
Jeff said he had someone looking into it. I'll track down who's working
on it.
Thanks,
Tony
next prev parent reply other threads:[~2020-07-31 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 17:09 [net 0/2][pull request] Intel Wired LAN Driver Updates 2020-07-30 Tony Nguyen
2020-07-30 17:09 ` [net 1/2] e1000e: continue to init PHY even when failed to disable ULP Tony Nguyen
2020-07-30 17:09 ` [net 2/2] igb: reinit_locked() should be called with rtnl_lock Tony Nguyen
2020-07-30 23:27 ` [net 0/2][pull request] Intel Wired LAN Driver Updates 2020-07-30 Jakub Kicinski
2020-07-31 15:33 ` Nguyen, Anthony L [this message]
2020-07-31 23:52 ` David Miller
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=2e85c879b30f39cfb1ce3fab11cd7178179d51fe.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
/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).