From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Caspar Zhang <caspar@casparzhang.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 1/3] s/Tst_count/tst_count/ to avoid CamelCase
Date: Thu, 07 Mar 2013 16:33:12 +0800 [thread overview]
Message-ID: <513850C8.9080905@cn.fujitsu.com> (raw)
In-Reply-To: <499128d9e24439238b64dc1740ee9e7217ec953f.1362641893.git.caspar@casparzhang.com>
On 03/07/2013 03:38 PM, Caspar Zhang wrote:
> when using latest checkpatch.pl, CamelCase variables are not encouraged,
> this patch does a batch update to replace all var `Tst_count` with
> `tst_count`.
>
> Signed-off-by: Caspar Zhang <caspar@casparzhang.com>
Hope this won't break anything.
Acked-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-03-07 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 7:38 [LTP] [PATCH 1/3] s/Tst_count/tst_count/ to avoid CamelCase Caspar Zhang
2013-03-07 7:38 ` [LTP] [PATCH 2/3] syscalls/madvise: code cleanup Caspar Zhang
2013-03-07 8:27 ` Wanlong Gao
2013-03-07 7:38 ` [LTP] [PATCH 3/3] syscalls/madvise02: fix madvise case due to kernel change Caspar Zhang
2013-03-07 8:17 ` Wanlong Gao
2013-03-07 8:20 ` Caspar Zhang
2013-03-07 8:24 ` Zhouping Liu
2013-03-07 8:33 ` Wanlong Gao [this message]
2013-03-07 8:32 ` [LTP] [PATCH 1/3] s/Tst_count/tst_count/ to avoid CamelCase Caspar Zhang
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=513850C8.9080905@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=caspar@casparzhang.com \
--cc=ltp-list@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 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.