[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160712132359.7eec5002@gandalf.local.home>
Date: Tue, 12 Jul 2016 13:23:59 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, idosch@...lanox.com,
yotamg@...lanox.com, eladr@...lanox.com, nogahf@...lanox.com,
ogerlitz@...lanox.com, ivecera@...hat.com, mingo@...hat.com,
jolsa@...nel.org
Subject: Re: [patch net-next v2 1/2] devlink: add hardware messages tracing
facility
On Tue, 12 Jul 2016 19:10:46 +0200
Jiri Pirko <jiri@...nulli.us> wrote:
> Tue, Jul 12, 2016 at 06:38:26PM CEST, rostedt@...dmis.org wrote:
> >On Tue, 12 Jul 2016 18:05:03 +0200
> >Jiri Pirko <jiri@...nulli.us> wrote:
> >
> >> From: Jiri Pirko <jiri@...lanox.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@...lanox.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
Powered by blists - more mailing lists