linux-kernel - Re: [PATCH] tracing: Correct braces usage in if-else statement

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANWV4VmqxZYMP26fV+Dt3h6LubyYppdgpxkRxetmtJOZbpzYkA@mail.gmail.com>
Date:	Sun, 20 Apr 2014 01:09:15 +0800
From:	ivan lin <linyongting@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Frédéric Weisbecker <fweisbec@...il.com>,
	mingo@...hat.com, linux-kernel@...r.kernel.org,
	linyongting@...wei.com
Subject: Re: [PATCH] tracing: Correct braces usage in if-else statement

2014-04-19 23:28 GMT+08:00 Steven Rostedt <rostedt@...dmis.org>:
> On Sat, 19 Apr 2014 21:58:23 +0800
> Lin Yongting <linyongting@...il.com> wrote:
>
>> There are some incorrect braces usages in kernerl/trace/trace.c, including:
>> 1. Missing braces in 'if' or 'else' branch.
>> 2. Unnecessary braces in 'if' statement.
>>
>> Fix them according to kernel CodeStyle.
>
> I understand that this is part of the CodeStyle, but I'm not accepting
> this patch. It causes more pain than it is worth, as it makes it more
> difficult to see git history because of "clean up" changes that get in
> the way. I also honestly don't think this is much of a clean up.
>
> Sorry,
>
> -- Steve
>

Yes, you are right.  This clean up is pain than it is worth.

Thnaks!

-- Yongting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/