From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752134Ab1GXCb2 (ORCPT ); Sat, 23 Jul 2011 22:31:28 -0400 Received: from mail-pz0-f42.google.com ([209.85.210.42]:64199 "EHLO mail-pz0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751938Ab1GXCbW (ORCPT ); Sat, 23 Jul 2011 22:31:22 -0400 From: Zac Storer To: rdunlap@xenotime.net Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Zac Storer Subject: [PATCH] Documentation: SubmittingPatches: fixed a spelling error Date: Sat, 23 Jul 2011 20:31:09 -0600 Message-Id: <1311474669-26947-1-git-send-email-zac.3.14159@gmail.com> X-Mailer: git-send-email 1.7.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Fixed a spelling error. Signed-off-by: Zac Storer --- Documentation/SubmittingPatches | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 569f353..4468ce2 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -303,7 +303,7 @@ patches that are being emailed around. The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to -pass it on as a open-source patch. The rules are pretty simple: if you +pass it on as an open-source patch. The rules are pretty simple: if you can certify the below: Developer's Certificate of Origin 1.1 -- 1.7.6