linux-kernel - Re: [PATCH] fix whitespace errors found by checkpatch.pl

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: <20150317.152112.1902057116873296620.davem@redhat.com>
Date:	Tue, 17 Mar 2015 15:21:12 -0400 (EDT)
From:	David Miller <davem@...hat.com>
To:	kevin@...inmulvey.net
Cc:	kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
	kaber@...sh.net, steffen.klassert@...unet.com,
	herbert@...dor.apana.org.au, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, kmulvey@...ux.com
Subject: Re: [PATCH] fix whitespace errors found by checkpatch.pl

From: Kevin Mulvey <kevin@...inmulvey.net>
Date: Tue, 17 Mar 2015 07:54:47 -0400

> make checkpatch happier by fixing some whitespace
> in ip6_tunnel.c and ip6_vti.c
> 
> Signed-off-by: Kevin Mulvey <kmulvey@...ux.com>

Your Subject line should specify a subsystem prefix, followed by a colon
character, indicating the area of the kernel where you are making
changes.

In this particular case, "ipv6: " would be an appropriate one to use.

Otherwise in the shortlog, it is impossible to determine where a commit
might be making changes.
--
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/