From: Varka Bhadram <varkabhadram@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>,
"Alexander Aring" <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH] ieee802154: Add trace events for rdev->ops
Date: Fri, 17 Apr 2015 17:19:58 +0530 [thread overview]
Message-ID: <5530F366.4030407@gmail.com> (raw)
In-Reply-To: <20150412120733.GA6181@bogon.m.sigxcpu.org>
On 04/12/2015 05:37 PM, Guido Günther wrote:
> This is based on the rdev->ops tracing code from net/wireless/.
Instead of writing the above commit message its better to write
what exactly this code is for and how can we use this from
the user space (if possible with commands).
If you want to write your above commit message put it in trace.c/h file
> Signed-off-by: Guido Günther <agx@sigxcpu.org>
> ---
> net/ieee802154/Makefile | 4 +-
> net/ieee802154/rdev-ops.h | 77 ++++++++++++---
> net/ieee802154/trace.c | 7 ++
> net/ieee802154/trace.h | 243 ++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 319 insertions(+), 12 deletions(-)
> create mode 100644 net/ieee802154/trace.c
> create mode 100644 net/ieee802154/trace.h
>
> diff --git a/net/ieee802154/Makefile b/net/ieee802154/Makefile
> index 05dab29..4adfd4d 100644
> --- a/net/ieee802154/Makefile
> +++ b/net/ieee802154/Makefile
> @@ -3,7 +3,9 @@ obj-$(CONFIG_IEEE802154_SOCKET) += ieee802154_socket.o
> obj-y += 6lowpan/
>
> ieee802154-y := netlink.o nl-mac.o nl-phy.o nl_policy.o core.o \
> - header_ops.o sysfs.o nl802154.o
> + header_ops.o sysfs.o nl802154.o trace.o
> ieee802154_socket-y := socket.o
>
> +CFLAGS_trace.o := -I$(src)
What is this for..?
--
Varka Bhadram
next prev parent reply other threads:[~2015-04-17 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 12:07 [PATCH] ieee802154: Add trace events for rdev->ops Guido Günther
2015-04-17 10:03 ` Alexander Aring
2015-04-17 10:32 ` Alexander Aring
2015-04-17 10:27 ` Alexander Aring
2015-04-20 18:36 ` Guido Günther
2015-04-17 11:49 ` Varka Bhadram [this message]
2015-04-20 18:35 ` Guido Günther
2015-04-20 18:50 ` 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=5530F366.4030407@gmail.com \
--to=varkabhadram@gmail.com \
--cc=agx@sigxcpu.org \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
/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