public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
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 0/3] bnxt_en: Bug fixes
Date: Fri, 18 Jun 2021 19:10:03 +0000	[thread overview]
Message-ID: <162404340379.6189.8018755889955505608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1623996447-28958-1-git-send-email-michael.chan@broadcom.com>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Fri, 18 Jun 2021 02:07:24 -0400 you wrote:
> This patchset includes 3 small bug fixes to reinitialize PHY capabilities
> after firmware reset, setup the chip's internal TQM fastpath ring
> backing memory properly for RoCE traffic, and to free ethtool related
> memory if driver probe fails.
> 
> Michael Chan (1):
>   bnxt_en: Rediscover PHY capabilities after firmware reset
> 
> [...]

Here is the summary with links:
  - [net,1/3] bnxt_en: Rediscover PHY capabilities after firmware reset
    https://git.kernel.org/netdev/net/c/0afd6a4e8028
  - [net,2/3] bnxt_en: Fix TQM fastpath ring backing store computation
    https://git.kernel.org/netdev/net/c/c12e1643d273
  - [net,3/3] bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
    https://git.kernel.org/netdev/net/c/03400aaa69f9

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2021-06-18 19:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  6:07 [PATCH net 0/3] bnxt_en: Bug fixes Michael Chan
2021-06-18  6:07 ` [PATCH net 1/3] bnxt_en: Rediscover PHY capabilities after firmware reset Michael Chan
2021-06-18  6:07 ` [PATCH net 2/3] bnxt_en: Fix TQM fastpath ring backing store computation Michael Chan
2021-06-18  6:07 ` [PATCH net 3/3] bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path Michael Chan
2021-06-18 19:10 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-29 23:25 [PATCH net 0/3] bnxt_en: Bug fixes Michael Chan
2025-06-13 23:18 Michael Chan
2025-06-17 23:10 ` patchwork-bot+netdevbpf
2024-04-05 23:55 Michael Chan
2024-04-08 13:00 ` patchwork-bot+netdevbpf
2022-05-03  1:13 Michael Chan
2022-05-04  1:00 ` patchwork-bot+netdevbpf
2021-11-15  7:37 Michael Chan
2021-11-15 14:20 ` patchwork-bot+netdevbpf
2021-09-12 16:34 Michael Chan
2021-09-13 11:40 ` patchwork-bot+netdevbpf
2020-05-25 21:41 Michael Chan
2020-05-27  3:31 ` David Miller
2020-01-17  5:32 Michael Chan
2020-01-18 13:48 ` David Miller
2018-09-03  8:23 Michael Chan
2018-09-04  5:01 ` David Miller
2018-09-04  5:50   ` Michael Chan
2018-09-04  6:30     ` Michael Chan
2017-08-23 23:34 [PATCH net 0/3] bnxt_en: bug fixes Michael Chan
2017-08-24  5:42 ` David Miller
2017-07-11 17:05 [PATCH net 0/3] bnxt_en: Bug fixes Michael Chan
2017-07-11 17:32 ` David Miller
2016-06-06  6:37 Michael Chan
2016-06-07 23:02 ` David Miller
2016-01-28  8:11 Michael Chan
2016-01-30  1:28 ` 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=162404340379.6189.8018755889955505608.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=gospo@broadcom$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=michael.chan@broadcom$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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