Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-wpan@vger.kernel.org, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH bluetooth-next] cfg802154: fix rdev-ops naming convension and format specifiers
Date: Wed, 3 Jun 2015 09:00:28 +0200	[thread overview]
Message-ID: <20150603070025.GC731@omega> (raw)
In-Reply-To: <1433303507-10061-1-git-send-email-varkab@cdac.in>

On Wed, Jun 03, 2015 at 09:21:47AM +0530, Varka Bhadram wrote:
> This patch make to use the same naming convention that mac802154
> tracing follows and fixes the format specifier for extended addr.
> 
> Signed-off-by: Varka Bhadram <varkab@cdac.in>

Acked-by: Alexander Aring <alex.aring@gmail.com>

  reply	other threads:[~2015-06-03  7:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  3:51 [PATCH bluetooth-next] cfg802154: fix rdev-ops naming convension and format specifiers Varka Bhadram
2015-06-03  7:00 ` Alexander Aring [this message]
2015-06-03  9:34 ` Marcel Holtmann

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