From: Caspar Zhang <caspar@casparzhang.com>
To: gaowanlong@cn.fujitsu.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:32:41 +0800 [thread overview]
Message-ID: <513850A9.2070807@casparzhang.com> (raw)
In-Reply-To: <513850C8.9080905@cn.fujitsu.com>
On 03/07/2013 04:33 PM, Wanlong Gao wrote:
> 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>
>
Tested by compiling all the patched cases, everything seems still working.
Caspar
------------------------------------------------------------------------------
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
prev parent reply other threads:[~2013-03-07 8:32 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 ` [LTP] [PATCH 1/3] s/Tst_count/tst_count/ to avoid CamelCase Wanlong Gao
2013-03-07 8:32 ` Caspar Zhang [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=513850A9.2070807@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=gaowanlong@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox