From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, idosch@mellanox.com,
yotamg@mellanox.com, eladr@mellanox.com, nogahf@mellanox.com,
ogerlitz@mellanox.com, ivecera@redhat.com, mingo@redhat.com,
jolsa@kernel.org
Subject: Re: [patch net-next v2 1/2] devlink: add hardware messages tracing facility
Date: Tue, 12 Jul 2016 13:23:59 -0400 [thread overview]
Message-ID: <20160712132359.7eec5002@gandalf.local.home> (raw)
In-Reply-To: <20160712171046.GA1799@nanopsycho.orion>
On Tue, 12 Jul 2016 19:10:46 +0200
Jiri Pirko <jiri@resnulli.us> wrote:
> Tue, Jul 12, 2016 at 06:38:26PM CEST, rostedt@goodmis.org wrote:
> >On Tue, 12 Jul 2016 18:05:03 +0200
> >Jiri Pirko <jiri@resnulli.us> wrote:
> >
> >> From: Jiri Pirko <jiri@mellanox.com>
> >>
> >> Define a tracepoint and allow user to trace messages going to and from
> >> hardware associated with devlink instance.
> >>
> >> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
> >> ---
> >> v1->v2:
> >> - Use EXPORT_TRACEPOINT_SYMBOL_GPL instead of a wrapper function
> >> as suggested by David Ahern and Steven Rostedt
> >
> >FYI, you can use the Suggested-by: tag too ;-)
>
> Thought that the purpose of that tag is if someone suggested the whole
> patch existence.
Yeah, it has different meanings. You could always be creative and add:
Parts-suggested-by: ....
;-)
-- Steve
next prev parent reply other threads:[~2016-07-12 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 16:05 [patch net-next v2 1/2] devlink: add hardware messages tracing facility Jiri Pirko
2016-07-12 16:05 ` [patch net-next v2 2/2] mlxsw: core: Trace EMAD messages Jiri Pirko
2016-07-12 21:20 ` David Miller
2016-07-12 16:38 ` [patch net-next v2 1/2] devlink: add hardware messages tracing facility Steven Rostedt
2016-07-12 17:10 ` Jiri Pirko
2016-07-12 17:23 ` Steven Rostedt [this message]
2016-07-12 21:20 ` 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=20160712132359.7eec5002@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=jolsa@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=yotamg@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).