From: David Miller <davem@davemloft.net>
To: idosch@mellanox.com
Cc: netdev@vger.kernel.org, jiri@mellanox.com, nird@mellanox.com,
mlxsw@mellanox.com
Subject: Re: [PATCH net-next 0/2] mlxsw: core: Trace EMAD errors
Date: Wed, 06 Feb 2019 11:26:18 -0800 (PST) [thread overview]
Message-ID: <20190206.112618.1549501499140458869.davem@davemloft.net> (raw)
In-Reply-To: <20190204184649.5292-1-idosch@mellanox.com>
From: Ido Schimmel <idosch@mellanox.com>
Date: Mon, 4 Feb 2019 18:47:44 +0000
> Nir says:
>
> This patchset adds a trace for EMAD errors to the existing EMAD payload
> traces. This tracepoint is useful to track user or firmware errors during
> tests execution.
>
> Patch #1 defines the devlink tracepoint.
> Patch #2 uses it for reporting mlxsw EMAD errors.
Series applied, thanks.
prev parent reply other threads:[~2019-02-06 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 18:47 [PATCH net-next 0/2] mlxsw: core: Trace EMAD errors Ido Schimmel
2019-02-04 18:47 ` [PATCH net-next 1/2] devlink: add hardware errors tracing facility Ido Schimmel
2019-02-04 18:47 ` [PATCH net-next 2/2] mlxsw: core: Trace EMAD errors Ido Schimmel
2019-02-06 19:26 ` David Miller [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=20190206.112618.1549501499140458869.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nird@mellanox.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).