All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH v2] ieee802154: Add trace events for rdev->ops
Date: Sat, 25 Apr 2015 08:45:51 +0200	[thread overview]
Message-ID: <20150425064550.GA3395@omega> (raw)
In-Reply-To: <20150423194532.GA2902@bogon.m.sigxcpu.org>

Hi,

On Thu, Apr 23, 2015 at 09:45:32PM +0200, Guido Günther wrote:
> Hi,
> On Wed, Apr 22, 2015 at 10:09:37AM +0200, Alexander Aring wrote:
> > On Mon, Apr 20, 2015 at 08:36:56PM +0200, Guido Günther wrote:
> > > Enabling tracing via
> > > 
> > >  echo 1 > /sys/kernel/debug/tracing/events/cfg802154/enable
> > > 
> > > enables event tracing like
> > > 
> > >  iwpan dev wpan0 set pan_id 0xbeef
> > >  cat /sys/kernel/debug/tracing/trace
> > >  # tracer: nop
> > >  #
> > >  # entries-in-buffer/entries-written: 2/2   #P:1
> > >  #
> > >  #                              _-----=> irqs-off
> > >  #                             / _----=> need-resched
> > >  #                            | / _---=> hardirq/softirq
> > >  #                            || / _--=> preempt-depth
> > >  #                            ||| /     delay
> > >  #           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
> > >  #              | |       |   ||||       |         |
> > >             iwpan-2663  [000] ....   170.369142: 802154_rdev_set_pan_id: phy0, wpan_dev(1), pan id: 0xbeef
> > >             iwpan-2663  [000] ....   170.369177: 802154_rdev_return_int: phy0, returned: 0
> > > 
> > > Signed-off-by: Guido Günther <agx@sigxcpu.org>
> > 
> > Acked-by: Alexander Aring <alex.aring@gmail.com>
> 
> Thanks for reviewing!  Is there any procedure to get these queued for
> bluetooth-next? Are you forwarding such patches to Marcel?

no. The current situation was a conclusion that we had massive changes
inside the generic 6LoWPAN branch (net/6lowpan) which is used by
ble/802.15.4 . For easier applying without conflicts marcel offers his
help to apply everything and I think he has actual a nice setup with:

 - some creat testing evironment which checks if patch apply and run
   tests on it.

 - klick one button to send "thanks applied" mail and apply the patch on
   his bluetooth branch and send a push. (maybe on his iPad ;-))

Currently I don't have such setup environment, but I need something like
that. When the time allows then I will try to build something like that.


What I do now is to have a private queue, if Marcel doesn't repsond ~2
weeks after the "Acked-by" then I will send a "ping". I think every
maintainer have a timeslot to making his/her "rounds" on the mailinglist
to grab patches. I am not forwarding the patches to marcel, he will
apply the patches from linux-wpan or netdev mailinglist.

The time will come when linux-wpan have his own repository and send then
pull-request to Marcel (if there are too many shared code between
802.15.4 and bt) or netdev.

- Alex

      reply	other threads:[~2015-04-25  6:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 18:36 [PATCH v2] ieee802154: Add trace events for rdev->ops Guido Günther
2015-04-22  8:09 ` Alexander Aring
2015-04-23 19:45   ` Guido Günther
2015-04-25  6:45     ` Alexander Aring [this message]

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=20150425064550.GA3395@omega \
    --to=alex.aring@gmail.com \
    --cc=agx@sigxcpu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.