netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: michael.chan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] bnxt_en: 2 bug fixes.
Date: Sun, 01 Mar 2020 19:17:26 -0800 (PST)	[thread overview]
Message-ID: <20200301.191726.2066352230110487395.davem@davemloft.net> (raw)
In-Reply-To: <1583118438-18829-1-git-send-email-michael.chan@broadcom.com>

From: Michael Chan <michael.chan@broadcom.com>
Date: Sun,  1 Mar 2020 22:07:16 -0500

> This first patch fixes a rare but possible crash in pci_disable_msix()
> when the MTU is changed.  The 2nd patch fixes a regression in error
> code handling when flashing a file to NVRAM.

Applied.

> Please also queue these for -stable.  Thanks.

Queued up, thanks Michael.

  parent reply	other threads:[~2020-03-02  3:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02  3:07 [PATCH net 0/2] bnxt_en: 2 bug fixes Michael Chan
2020-03-02  3:07 ` [PATCH net 1/2] bnxt_en: reinitialize IRQs when MTU is modified Michael Chan
2020-03-02  3:07 ` [PATCH net 2/2] bnxt_en: fix error handling when flashing from file Michael Chan
2020-03-02  3:17 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-04  4:38 [PATCH net 0/2] bnxt_en: 2 Bug fixes Michael Chan
2025-01-07  0:50 ` patchwork-bot+netdevbpf
2023-03-04  2:43 [PATCH net 0/2] bnxt_en: 2 bug fixes Michael Chan
2023-03-06 21:30 ` patchwork-bot+netdevbpf
2021-08-15 20:15 Michael Chan
2021-08-16 10:40 ` patchwork-bot+netdevbpf
2021-05-15  7:25 Michael Chan
2021-05-17 21:10 ` patchwork-bot+netdevbpf
2021-02-11  7:24 Michael Chan
2021-02-11 22:50 ` patchwork-bot+netdevbpf
2019-04-08 21:39 Michael Chan
2019-04-08 23:39 ` David Miller
2016-11-11  5:11 Michael Chan
2016-11-13 17:37 ` David Miller
2016-05-04 20:56 Michael Chan
2016-05-04 21:12 ` 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=20200301.191726.2066352230110487395.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).