linux-kernel - Re: [patch trivial] fix typo in Documentation/SubmittingPatches

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: <20070824084651.71a5c592.randy.dunlap@oracle.com>
Date:	Fri, 24 Aug 2007 08:46:51 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	andre@...ow14.de
Cc:	trivial@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch trivial] fix typo in Documentation/SubmittingPatches

On Fri, 24 Aug 2007 11:45:13 +0200 andre@...ow14.de wrote:

> From: Andre Haupt <andre@...ow14.de>
> Signed-off-by: Andre Haupt <andre@...ow14.de>

Acked-by: Randy Dunlap <randy.dunlap@...cle.com>

> ---
> Index: linus/Documentation/SubmittingPatches
> ===================================================================
> --- linus.orig/Documentation/SubmittingPatches	2007-08-24 11:12:33.000000000 +0200
> +++ linus/Documentation/SubmittingPatches	2007-08-24 11:13:51.000000000 +0200
> @@ -126,7 +126,7 @@
>  without even being read.
>  
>  At a minimum you should check your patches with the patch style
> -checker prior to submission (scripts/patchcheck.pl).  You should
> +checker prior to submission (scripts/checkpatch.pl).  You should
>  be able to justify all violations that remain in your patch.
>  
>  
> 


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/