All of lore.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/2] bnxt_en: Bug fixes.
Date: Mon, 28 Dec 2020 22:20:07 +0000	[thread overview]
Message-ID: <160919400700.29691.12531949239256214537.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1609096698-15009-1-git-send-email-michael.chan@broadcom.com>

Hello:

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

On Sun, 27 Dec 2020 14:18:16 -0500 you wrote:
> The first patch fixes recovery of fatal AER errors.  The second one
> fixes a potential array out of bounds issue.
> 
> Please queue for -stable.  Thanks.
> 
> Michael Chan (1):
>   bnxt_en: Check TQM rings for maximum supported value.
> 
> [...]

Here is the summary with links:
  - [net,1/2] bnxt_en: Fix AER recovery.
    https://git.kernel.org/netdev/net/c/fb1e6e562b37
  - [net,2/2] bnxt_en: Check TQM rings for maximum supported value.
    https://git.kernel.org/netdev/net/c/a029a2fef5d1

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



  parent reply	other threads:[~2020-12-28 23:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-27 19:18 [PATCH net 0/2] bnxt_en: Bug fixes Michael Chan
2020-12-27 19:18 ` [PATCH net 1/2] bnxt_en: Fix AER recovery Michael Chan
2020-12-27 19:18 ` [PATCH net 2/2] bnxt_en: Check TQM rings for maximum supported value Michael Chan
2020-12-28 22:20 ` patchwork-bot+netdevbpf [this message]
2021-01-11  9:26 [PATCH net 0/2] bnxt_en: Bug fixes Michael Chan
2021-01-13  4:10 ` patchwork-bot+netdevbpf
2023-04-17  6:58 Michael Chan
2023-04-18 10: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=160919400700.29691.12531949239256214537.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.