From 49070981887259cf2e1093bd8880e48fc630580e Mon Sep 17 00:00:00 2001 From: Andre Haupt Date: Tue, 11 Sep 2007 15:23:47 -0700 Subject: [PATCH] --- yaml --- r: 64870 b: refs/heads/master c: a570ab6f10462b062c28188b64377b8034235761 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/SubmittingPatches | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 7904835a3c58..7e70abd04572 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: a83308e60f63749dc1d08acb0d8fa9e2ec13c9a7 +refs/heads/master: a570ab6f10462b062c28188b64377b8034235761 diff --git a/trunk/Documentation/SubmittingPatches b/trunk/Documentation/SubmittingPatches index 397575880dc4..a30dd4480ad4 100644 --- a/trunk/Documentation/SubmittingPatches +++ b/trunk/Documentation/SubmittingPatches @@ -126,7 +126,7 @@ the reviewers time and will get your patch rejected, probably 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.