linux-kernel - Re: [PATCH V2 1/4] staging: vt6556: Cleanup coding style issues

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 Jul 2014 19:01:37 +0200
From:	Peter Senna Tschudin <peter.senna@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>, devel@...verdev.osuosl.org,
	Malcolm Priestley <tvboxspy@...il.com>,
	kernel-janitors@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Forest Bond <forest@...ttletooquiet.net>
Subject: Re: [PATCH V2 1/4] staging: vt6556: Cleanup coding style issues

<note>
I'm not trying to push my changes over the rules. I'm trying to
understand the problem, to avoid creating similar noise in the future.
</note>

Now I understand that the problem with the series of 4 patches is that
the subject is the same on the 4 patches. Having the same subject in 4
patches is not good. I got this one.

But I have no clue why joining 4 cleanup patches into 1 is bad. The
patches are all for the same driver, are all silencing checkpatch
warnings, and even the typedef stuff was reported by checkpatch. The
commit message of the single patch describes it all. If the subject of
the series is the problem, why not make a single patch instead of a
series of similar patches? It made sense from my perspective. So what
is the problem in re-submit 4 similar patches as a single patch?

On Mon, Jul 14, 2014 at 4:12 PM, Dan Carpenter <dan.carpenter@...cle.com> wrote:
> Since you're going to redo this patch anyway, I may as well give you
> the normal feedback for these kinds of patches.
>
>> >From 69cd87aca39730c0578592d1296b738f7f223f29 Mon Sep 17 00:00:00 2001
>> From: Peter Senna Tschudin <peter.senna@...il.com>
>> Date: Mon, 14 Jul 2014 10:28:42 +0200
>> Subject: [PATCH V3] staging: vt6556: Cleanup coding style issues
>>
>> This patch cleanup coding style issues reported by checkpatch.
>>
>> This typedef, reported by checkpatch, was removed from card.h:
>> typedef enum _CARD_PHY_TYPE {
>>     PHY_TYPE_AUTO = 0,
>>     PHY_TYPE_11B,
>>     PHY_TYPE_11G,
>>     PHY_TYPE_11A
>> } CARD_PHY_TYPE, *PCARD_PHY_TYPE;
>>
>> The following typedefs were removed, but enums were kept at device.h:
>>  - typedef enum __device_msg_level
>>  - typedef enum __DEVICE_NDIS_STATUS
>>
>
> Break this kind of patch into patches which fix one type of mistake per
> patch:
> patch 1: fix whitespace stuff
> patch 2: remove useless returns
> patch 3: remove typedefs
> etc.
>
>> -//{{RobertYu:20060515, new BB setting for VT3226D0
>> +/* {{RobertYu:20060515, new BB setting for VT3226D0 */
>
> Just delete these, because we have version control.
>
> regards,
> dan carpenter
>



-- 
Peter
--
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/