From: "santosh.anbu" <asantoshking@gmail.com>
To: ericvh@gmail.com
Cc: asantosh.king@gmail.com, linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: [PATCH] Events: 9p.h: Fixed few brace coding style issues
Date: Mon, 29 Jul 2013 22:51:08 +0530 [thread overview]
Message-ID: <1375118468-3349-1-git-send-email-asantosh.king@gmail.com> (raw)
From: "santosh.anbu" <asantosh.king@gmail.com>
Kill all the whitespaces conforming to standards
Signed-off-by: santosh.anbu <asantosh.king@gmail.com>
---
include/trace/events/9p.h | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/include/trace/events/9p.h b/include/trace/events/9p.h
index a066636..c91a015 100644
--- a/include/trace/events/9p.h
+++ b/include/trace/events/9p.h
@@ -83,9 +83,9 @@ TRACE_EVENT(9p_client_req,
TP_ARGS(clnt, type, tag),
TP_STRUCT__entry(
- __field( void *, clnt )
- __field( __u8, type )
- __field( __u32, tag )
+ __field(void *, clnt)
+ __field(__u8, type)
+ __field(__u32, tag)
),
TP_fast_assign(
@@ -97,7 +97,7 @@ TRACE_EVENT(9p_client_req,
TP_printk("client %lu request %s tag %d",
(long)__entry->clnt, show_9p_op(__entry->type),
__entry->tag)
- );
+);
TRACE_EVENT(9p_client_res,
TP_PROTO(struct p9_client *clnt, int8_t type, int tag, int err),
@@ -105,10 +105,10 @@ TRACE_EVENT(9p_client_res,
TP_ARGS(clnt, type, tag, err),
TP_STRUCT__entry(
- __field( void *, clnt )
- __field( __u8, type )
- __field( __u32, tag )
- __field( __u32, err )
+ __field(void *, clnt)
+ __field(__u8, type)
+ __field(__u32, tag)
+ __field(__u32, err)
),
TP_fast_assign(
@@ -131,10 +131,10 @@ TRACE_EVENT(9p_protocol_dump,
TP_ARGS(clnt, pdu),
TP_STRUCT__entry(
- __field( void *, clnt )
- __field( __u8, type )
- __field( __u16, tag )
- __array( unsigned char, line, P9_PROTO_DUMP_SZ )
+ __field(void *, clnt)
+ __field(__u8, type)
+ __field(__u16, tag)
+ __array(unsigned char, line, P9_PROTO_DUMP_SZ)
),
TP_fast_assign(
@@ -146,7 +146,7 @@ TRACE_EVENT(9p_protocol_dump,
TP_printk("clnt %lu %s(tag = %d)\n%.3x: %16ph\n%.3x: %16ph\n",
(unsigned long)__entry->clnt, show_9p_op(__entry->type),
__entry->tag, 0, __entry->line, 16, __entry->line + 16)
- );
+);
#endif /* _TRACE_9P_H */
--
1.8.1.2
reply other threads:[~2013-07-29 17:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1375118468-3349-1-git-send-email-asantosh.king@gmail.com \
--to=asantoshking@gmail.com \
--cc=asantosh.king@gmail.com \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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
Powered by JetHome