Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Varka Bhadram <varkab@cdac.in>
To: Alexander Aring <alex.aring@gmail.com>,
	Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [RFC bluetooth-next] mac802154: add trace functionality for driver ops
Date: Fri, 29 May 2015 11:50:22 +0530	[thread overview]
Message-ID: <55680526.5000403@cdac.in> (raw)
In-Reply-To: <20150529061923.GA1467@omega>

On 05/29/2015 11:49 AM, Alexander Aring wrote:
> On Fri, May 29, 2015 at 11:01:48AM +0530, Varka Bhadram wrote:
>> Hi Alex,
>>
>> On 05/28/2015 01:50 PM, Alexander Aring wrote:
>>
>>> Hi,
>>>
>>> I did not test yet, but found some review things.
>> Please test it.
>>
>>> On Wed, May 27, 2015 at 01:54:50PM +0530, Varka Bhadram wrote:
>>> ...
>>>> +		__field(bool, mode)
>>>> +	),
>>>> +	TP_fast_assign(
>>>> +		LOCAL_ASSIGN;
>>>> +		__entry->mode = mode;
>>>> +	),
>>>> +	TP_printk(LOCAL_PR_FMT ", lbt mode: %s", LOCAL_PR_ARG,
>>>> +		  BOOL_TO_STR(__entry->mode))
>>>> +);
>>>> +
>>>> +TRACE_EVENT(802154_drv_set_short_addr,
>>>> +	TP_PROTO(struct ieee802154_local *local, __le16 short_addr),
>>>> +	TP_ARGS(local, short_addr),
>>>> +	TP_STRUCT__entry(
>>>> +		LOCAL_ENTRY
>>>> +		__field(__le16, short_addr)
>>>> +	),
>>>> +	TP_fast_assign(
>>>> +		LOCAL_ASSIGN;
>>>> +		__entry->short_addr = short_addr;
>>>> +	),
>>>> +	TP_printk(LOCAL_PR_FMT ", sa: 0x%04x", LOCAL_PR_ARG,
>>>> +		  __entry->short_addr)
>>> care about byteorder here. you need cpu_to_le16 in the format string,
>>> please.
>>>
>>>
> meant s/cpu_to_le16/le16_to_cpu/

Got it.

-- 
Varka Bhadram


-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------


  reply	other threads:[~2015-05-29  6:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  8:24 [RFC bluetooth-next] mac802154: add trace functionality for driver ops Varka Bhadram
2015-05-28  8:20 ` Alexander Aring
2015-05-29  5:31   ` Varka Bhadram
2015-05-29  6:19     ` Alexander Aring
2015-05-29  6:20       ` Varka Bhadram [this message]
2015-05-31 13:22 ` Alexander Aring

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=55680526.5000403@cdac.in \
    --to=varkab@cdac.in \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=varkabhadram@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