From: Stefan Schmidt <stefan@osg.samsung.com>
To: Varka Bhadram <varkabhadram@gmail.com>, linux-wpan@vger.kernel.org
Cc: alex.aring@gmail.com, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH bluetooth-next 2/3] ieee802154: trace: fix name for extended address
Date: Mon, 01 Jun 2015 09:37:49 +0200 [thread overview]
Message-ID: <556C0BCD.5010408@osg.samsung.com> (raw)
In-Reply-To: <1433133238-16056-3-git-send-email-varkab@cdac.in>
Hello.
On 01/06/15 06:33, Varka Bhadram wrote:
> Signed-off-by: Varka Bhadram <varkab@cdac.in>
> ---
> net/ieee802154/trace.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ieee802154/trace.h b/net/ieee802154/trace.h
> index b4295fd..9b5eefc 100644
> --- a/net/ieee802154/trace.h
> +++ b/net/ieee802154/trace.h
> @@ -56,7 +56,7 @@ TRACE_EVENT(802154_rdev_add_virtual_intf,
> __entry->type = type;
> __entry->extended_addr = extended_addr;
> ),
> - TP_printk(WPAN_PHY_PR_FMT ", virtual intf name: %s, type: %d, ea %llx",
> + TP_printk(WPAN_PHY_PR_FMT ", virtual intf name: %s, type: %d, extended addr: %llx",
> WPAN_PHY_PR_ARG, __get_str(vir_intf_name), __entry->type,
> __le64_to_cpu(__entry->extended_addr))
> );
Please merge this with the third patch. Its really the same line and
fixes the output and format specifier. I don't see a need to have two
patches for this.
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-06-01 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 4:33 [PATCH bluetooth-next 0/3] rdev-ops trace fixes Varka Bhadram
2015-06-01 4:33 ` [PATCH bluetooth-next 1/3] ieee802154: trace: fix name for tx power value Varka Bhadram
2015-06-01 4:33 ` [PATCH bluetooth-next 2/3] ieee802154: trace: fix name for extended address Varka Bhadram
2015-06-01 7:37 ` Stefan Schmidt [this message]
2015-06-01 8:15 ` Alexander Aring
2015-06-01 8:41 ` Varka Bhadram
2015-06-01 4:33 ` [PATCH bluetooth-next 3/3] ieee802154: trace: fix extended addr format specifier Varka Bhadram
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=556C0BCD.5010408@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=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 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.