[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160712171046.GA1799@nanopsycho.orion>
Date: Tue, 12 Jul 2016 19:10:46 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Steven Rostedt <rostedt@...dmis.org>
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
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.
<snip>
>> +/* This part must be outside protection */
>> +#include <trace/define_trace.h>
>> +
>> +#else /* CONFIG_NET_DEVLINK */
>> +
>> +#if !defined(_TRACE_DEVLINK_H)
>> +#define _TRACE_DEVLINK_H
>
>Ah, I guess you do need header protection here.
Yes, you do.
>
>OK, looks good to me.
>
>Acked-by: Steven Rostedt <rostedt@...dmis.org>
Thanks Steven!
Powered by blists - more mailing lists