From: David Miller <davem@davemloft.net>
To: michael.chan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/4] bnxt_en: Bug fixes.
Date: Sun, 09 Dec 2018 11:47:26 -0800 (PST) [thread overview]
Message-ID: <20181209.114726.131155400511406893.davem@davemloft.net> (raw)
In-Reply-To: <1544356862-3462-1-git-send-email-michael.chan@broadcom.com>
From: Michael Chan <michael.chan@broadcom.com>
Date: Sun, 9 Dec 2018 07:00:58 -0500
> The first patch fixes a regression on CoS queue setup, introduced
> recently by the 57500 new chip support patches. The rest are
> fixes related to ring and resource accounting on the new 57500 chips.
Series applied.
next prev parent reply other threads:[~2018-12-09 19:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 12:00 [PATCH net 0/4] bnxt_en: Bug fixes Michael Chan
2018-12-09 12:00 ` [PATCH net 1/4] bnxt_en: Fix CNP CoS queue regression Michael Chan
2018-12-09 12:01 ` [PATCH net 2/4] bnxt_en: Keep track of reserved IRQs Michael Chan
2018-12-09 12:01 ` [PATCH net 3/4] bnxt_en: Fix NQ/CP rings accounting on the new 57500 chips Michael Chan
2018-12-09 12:01 ` [PATCH net 4/4] bnxt_en: Fix _bnxt_get_max_rings() for " Michael Chan
2018-12-09 19:47 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-22 23:12 [PATCH net 0/4] bnxt_en: Bug fixes Michael Chan
2019-05-23 1:03 ` David Miller
2020-02-02 7:41 Michael Chan
2020-02-03 23:22 ` Jakub Kicinski
2020-06-14 23:57 Michael Chan
2020-06-15 20:29 ` David Miller
2020-06-23 23:01 Michael Chan
2020-06-23 23:45 ` Jakub Kicinski
2020-06-24 3:15 ` David Miller
2020-11-16 0:27 Michael Chan
2020-11-17 1:44 ` Jakub Kicinski
2022-08-22 15:06 Michael Chan
2022-08-23 3:04 ` Jakub Kicinski
2022-08-23 22:40 ` patchwork-bot+netdevbpf
2022-11-03 23:33 Michael Chan
2022-11-05 2:40 ` 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=20181209.114726.131155400511406893.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).