linux-kernel - Re: [PATCH] Net ipv6: Fixed checkpatch errors

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: <20120511.180656.57416607962439989.davem@davemloft.net>
Date:	Fri, 11 May 2012 18:06:56 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	cristian.chilipirea@...il.com
Cc:	kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
	kaber@...sh.net, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, daniel.baluta@...il.com
Subject: Re: [PATCH] Net ipv6: Fixed checkpatch errors

From: Cristian Chilipirea <cristian.chilipirea@...il.com>
Date: Fri, 11 May 2012 19:55:00 +0300

> Fixed all of ERROR "foo* bar" should be "foo *bar"
> 
> Signed-off-by: Cristian Chilipirea <cristian.chilipirea@...il.com>

Don't ever do this.

This has already been fixed in my net-next tree since April 1st, which
is more than a month ago.  What this means is that you wrote your
patch against something other than reality and your patch won't apply
at all.

All non-bug-fix networking patches should be against the net-next
tree, doing otherwise is at your own peril.
--
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/