linux-kernel - Re: [PATCH 1/3] Remove trailing NULs from network bonding sysfs interface.

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:	Wed, 28 Nov 2007 09:47:21 +0100
From:	Wagner Ferenc <wferi@...f.hu>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org, wferi@...f.hu
Subject: Re: [PATCH 1/3] Remove trailing NULs from network bonding sysfs interface.

Randy Dunlap <randy.dunlap@...cle.com> writes:

> On Wed, 28 Nov 2007 01:49:54 +0100 =?utf-8?q?Ferenc_W=C3=A1gner?= wrote:
>
> Patches 1 & 3 use
>
> 	if (res) statement;
>
> but the preferred form is
>
> 	if (res)
> 		statement;
>
> Even if this style was already used in the source file, it should
> be cleaned up.

No principal problem.  So that I learn something useful: how should I
go about this?  I created the patches with git-format-patch, and they
depend on each other, so I'd rather not git-reset, if possible...

Can I just create a follow-up patch which fixes this stylistic issue?
-- 
Thanks,
Feri.
-
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/