linux-kernel - Re: [PATCH] drivers: wlan-ng: fixed a coding style issue

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]

Message-ID: <1474578224.8253.30.camel@perches.com>
Date:   Thu, 22 Sep 2016 14:03:44 -0700
From:   Joe Perches <joe@...ches.com>
To:     becher.jannik@...il.com, Andrey Utkin <andrey_utkin@...tmail.com>
Cc:     gregkh@...uxfoundation.org, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers: wlan-ng: fixed a coding style issue

On Thu, 2016-09-22 at 22:52 +0200, becher.jannik@...il.com wrote:
> I always wondered why I shouldn't make more than one change in a patch,
> but in all talks I watched they said that it's easier for them to merge
> small patches.
>
> So you think I should make one "big" patch and resend it?

Make separate patches for each "type" of change.

Here it would be removing unnecessary space before all
casts in the same file or for all specific driver files.