From: David Miller <davem@davemloft.net>
To: michael.chan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/6] bnxt_en: bug fixes.
Date: Sat, 14 Oct 2017 18:52:07 -0700 (PDT) [thread overview]
Message-ID: <20171014.185207.1094199524602291441.davem@davemloft.net> (raw)
In-Reply-To: <1507943374-13308-1-git-send-email-michael.chan@broadcom.com>
From: Michael Chan <michael.chan@broadcom.com>
Date: Fri, 13 Oct 2017 21:09:28 -0400
> Various bug fixes for the VF/PF link change logic, VF resource checking,
> potential firmware response corruption on NVRAM and DCB parameters,
> and reading the wrong register for PCIe link speed on the VF.
Series applied, thanks.
next prev parent reply other threads:[~2017-10-15 1:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 1:09 [PATCH net 0/6] bnxt_en: bug fixes Michael Chan
2017-10-14 1:09 ` [PATCH net 1/6] bnxt_en: Improve VF/PF link change logic Michael Chan
2017-10-14 1:09 ` [PATCH net 2/6] bnxt_en: Don't use rtnl lock to protect link change logic in workqueue Michael Chan
2017-10-14 1:09 ` [PATCH net 3/6] bnxt_en: Fix VF PCIe link speed and width logic Michael Chan
2017-10-14 1:09 ` [PATCH net 4/6] bnxt_en: Fix VF resource checking Michael Chan
2017-10-14 1:09 ` [PATCH net 5/6] bnxt_en: Fix possible corrupted NVRAM parameters from firmware response Michael Chan
2017-10-14 1:09 ` [PATCH net 6/6] bnxt_en: Fix possible corruption in DCB parameters from firmware Michael Chan
2017-10-15 1:52 ` David Miller [this message]
2018-07-09 6:24 [PATCH net 0/6] bnxt_en: Bug fixes Michael Chan
2018-07-09 23:28 ` David Miller
2018-11-15 8:25 Michael Chan
2018-11-15 17:40 ` David Miller
2019-08-16 22:33 Michael Chan
2019-08-18 20:06 ` David Miller
2020-09-21 1:08 Michael Chan
2020-09-21 2:05 ` David Miller
2023-06-07 7:54 Michael Chan
2023-06-08 9:20 ` patchwork-bot+netdevbpf
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=20171014.185207.1094199524602291441.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=michael.chan@broadcom.com \
--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).