From: Michael Chan <michael.chan@broadcom.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
Andrew Gospodarek <gospo@broadcom.com>
Subject: Re: [PATCH net-next 0/9] bnxt_en: Updates.
Date: Mon, 7 Mar 2022 15:56:29 -0800 [thread overview]
Message-ID: <CACKFLik9QKQfzJW2MHCpZ4jiTHCBb-d5NdfNDo+4PjqRZOJYfA@mail.gmail.com> (raw)
In-Reply-To: <20220307142719.1501043b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Mon, Mar 7, 2022 at 2:27 PM Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Sat, 5 Mar 2022 03:54:33 -0500 Michael Chan wrote:
> > This patch series contains mainly NVRAM related features. More
> > NVRAM error checking and logging are added when installing firmware
> > packages. A new devlink hw health report is now added to report
> > and diagnose NVRAM issues. Other miscellaneous patches include
> > reporting correctly cards that don't support link pause, adding
> > an internal unknown link state, and avoiding unnecessary link
> > toggle during firmware reset.
>
> The devlink parts are missing documentation, I'm not sure how it's
> supposed to operate and AFAICT it's not just a normal health reporter
> implementation.
Sorry, missed the documentation update. My colleagues will respond to
your other comments and we will add the documentation.
>
> Please stop posting patches during the weekend.
This is the first time I'm hearing that patches cannot be posted
during the weekend.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next prev parent reply other threads:[~2022-03-07 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 8:54 [PATCH net-next 0/9] bnxt_en: Updates Michael Chan
2022-03-05 8:54 ` [PATCH net-next 1/9] bnxt_en: refactor error handling of HWRM_NVM_INSTALL_UPDATE Michael Chan
2022-03-05 8:54 ` [PATCH net-next 2/9] bnxt_en: add more error checks to HWRM_NVM_INSTALL_UPDATE Michael Chan
2022-03-05 8:54 ` [PATCH net-next 3/9] bnxt_en: parse result field when NVRAM package install fails Michael Chan
2022-03-07 22:13 ` Jakub Kicinski
2022-03-05 8:54 ` [PATCH net-next 4/9] bnxt_en: introduce initial link state of unknown Michael Chan
2022-03-05 8:54 ` [PATCH net-next 5/9] bnxt_en: Properly report no pause support on some cards Michael Chan
2022-03-05 8:54 ` [PATCH net-next 6/9] bnxt_en: Eliminate unintended link toggle during FW reset Michael Chan
2022-03-05 8:54 ` [PATCH net-next 7/9] bnxt_en: Do not destroy health reporters during reset Michael Chan
2022-03-05 8:54 ` [PATCH net-next 8/9] bnxt_en: implement hw health reporter Michael Chan
2022-03-07 22:21 ` Jakub Kicinski
2022-03-05 8:54 ` [PATCH net-next 9/9] bnxt_en: add an nvm test for hw diagnose Michael Chan
2022-03-07 22:24 ` Jakub Kicinski
2022-03-05 11:20 ` [PATCH net-next 0/9] bnxt_en: Updates patchwork-bot+netdevbpf
2022-03-07 22:27 ` Jakub Kicinski
2022-03-07 23:56 ` Michael Chan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-18 8:56 Michael Chan
2019-11-18 22:09 ` Jakub Kicinski
2019-11-19 1:15 ` 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=CACKFLik9QKQfzJW2MHCpZ4jiTHCBb-d5NdfNDo+4PjqRZOJYfA@mail.gmail.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=gospo@broadcom.com \
--cc=kuba@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).