From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
gospo@broadcom.com
Subject: Re: [PATCH net-next v2 0/4] bnxt_en: Update for net-next
Date: Mon, 10 Jan 2022 00:30:16 +0000 [thread overview]
Message-ID: <164177461652.5269.18284372712524159669.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1641772485-10421-1-git-send-email-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 9 Jan 2022 18:54:41 -0500 you wrote:
> This series adds better error and debug logging for firmware messages.
> We now also use the firmware provided timeout value for long running
> commands instead of capping it to 40 seconds.
>
> Edwin Peer (4):
> bnxt_en: add dynamic debug support for HWRM messages
> bnxt_en: improve VF error messages when PF is unavailable
> bnxt_en: use firmware provided max timeout for messages
> bnxt_en: improve firmware timeout messaging
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] bnxt_en: add dynamic debug support for HWRM messages
https://git.kernel.org/netdev/net-next/c/8fa4219dba8e
- [net-next,v2,2/4] bnxt_en: improve VF error messages when PF is unavailable
https://git.kernel.org/netdev/net-next/c/662c9b22f5b5
- [net-next,v2,3/4] bnxt_en: use firmware provided max timeout for messages
https://git.kernel.org/netdev/net-next/c/bce9a0b79008
- [net-next,v2,4/4] bnxt_en: improve firmware timeout messaging
https://git.kernel.org/netdev/net-next/c/8c6f36d93449
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-01-10 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 23:54 [PATCH net-next v2 0/4] bnxt_en: Update for net-next Michael Chan
2022-01-09 23:54 ` [PATCH net-next v2 1/4] bnxt_en: add dynamic debug support for HWRM messages Michael Chan
2022-01-09 23:54 ` [PATCH net-next v2 2/4] bnxt_en: improve VF error messages when PF is unavailable Michael Chan
2022-01-09 23:54 ` [PATCH net-next v2 3/4] bnxt_en: use firmware provided max timeout for messages Michael Chan
2022-01-09 23:54 ` [PATCH net-next v2 4/4] bnxt_en: improve firmware timeout messaging Michael Chan
2022-01-10 0:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-17 17:24 [PATCH net-next v2 0/4] bnxt_en: Update for net-next Michael Chan
2025-04-22 9:10 ` 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=164177461652.5269.18284372712524159669.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.