linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: George Cherian <george.cherian@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<davem@davemloft.net>, <sgoutham@marvell.com>,
	<lcherian@marvell.com>, <gakula@marvell.com>,
	<masahiroy@kernel.org>, <willemdebruijn.kernel@gmail.com>,
	<saeed@kernel.org>
Subject: Re: [PATCHv3 net-next 0/3] Add devlink and devlink health reporters to
Date: Fri, 20 Nov 2020 15:06:18 -0800	[thread overview]
Message-ID: <20201120150618.4d1a5b55@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20201120062801.2821502-1-george.cherian@marvell.com>

On Fri, 20 Nov 2020 11:57:58 +0530 George Cherian wrote:
> Add basic devlink and devlink health reporters.
> Devlink health reporters are added for NPA and NIX blocks.
> These reporters report the error count in respective blocks.
> 
> Address Jakub's comment to add devlink support for error reporting.
> https://www.spinics.net/lists/netdev/msg670712.html

This series does not apply to net-next, please rebase and repost.

  parent reply	other threads:[~2020-11-20 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20  6:27 [PATCHv3 net-next 0/3] Add devlink and devlink health reporters to George Cherian
2020-11-20  6:27 ` [PATCHv3 net-next 1/3] octeontx2-af: Add devlink suppoort to af driver George Cherian
2020-11-20  6:28 ` [PATCHv3 net-next 2/3] octeontx2-af: Add devlink health reporters for NPA George Cherian
2020-11-20  6:28 ` [PATCHv3 net-next 3/3] octeontx2-af: Add devlink health reporters for NIX George Cherian
2020-11-20 23:06 ` Jakub Kicinski [this message]
2020-11-21  4:01 [PATCHv3 net-next 0/3] Add devlink and devlink health reporters to George Cherian

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=20201120150618.4d1a5b55@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=gakula@marvell.com \
    --cc=george.cherian@marvell.com \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeed@kernel.org \
    --cc=sgoutham@marvell.com \
    --cc=willemdebruijn.kernel@gmail.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).