From: patchwork-bot+netdevbpf@kernel.org
To: George Cherian <george.cherian@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
corbet@lwn.net
Subject: Re: [PATCH net-next 0/2] Add devlink health reporters for NIX block
Date: Thu, 21 Jan 2021 20:10:08 +0000 [thread overview]
Message-ID: <161125980846.10330.13299364305009726430.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210119100120.2614730-1-george.cherian@marvell.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 19 Jan 2021 15:31:18 +0530 you wrote:
> Devlink health reporters are added for the NIX block.
>
> Address Jakub's comment to add devlink support for error reporting.
> https://www.spinics.net/lists/netdev/msg670712.html
>
> This series is in continuation to
> https://www.spinics.net/lists/netdev/msg707798.html
>
> [...]
Here is the summary with links:
- [net-next,1/2] octeontx2-af: Add devlink health reporters for NIX
https://git.kernel.org/netdev/net-next/c/5ed66306eab6
- [net-next,2/2] docs: octeontx2: Add Documentation for NIX health reporters
https://git.kernel.org/netdev/net-next/c/d41b3365bda7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-01-21 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 10:01 [PATCH net-next 0/2] Add devlink health reporters for NIX block George Cherian
2021-01-19 10:01 ` [PATCH net-next 1/2] octeontx2-af: Add devlink health reporters for NIX George Cherian
2021-01-19 10:01 ` [PATCH net-next 2/2] docs: octeontx2: Add Documentation for NIX health reporters George Cherian
2021-01-21 20:10 ` patchwork-bot+netdevbpf [this message]
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=161125980846.10330.13299364305009726430.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=george.cherian@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@marvell.com \
/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).