From: Randy Dunlap <rdunlap@xenotime.net>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH][Trivial] SubmitChecklist update, fix spelling error
Date: Wed, 6 Jun 2007 08:31:45 -0700 [thread overview]
Message-ID: <20070606083145.0ed8b1ab.rdunlap@xenotime.net> (raw)
In-Reply-To: <200706061355.50161.jesper.juhl@gmail.com>
On Wed, 6 Jun 2007 13:55:48 +0200 Jesper Juhl wrote:
>
> This trivial patch makes the following changes to Documentation/SubmitChecklist :
>
> - "sumbittal" is not a word, replace with "submission".
> - Remove a blank line, two should be enough.
>
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
> ---
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
> Documentation/SubmitChecklist | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/SubmitChecklist b/Documentation/SubmitChecklist
> index 6ebffb5..19e7f65 100644
> --- a/Documentation/SubmitChecklist
> +++ b/Documentation/SubmitChecklist
> @@ -1,4 +1,4 @@
> -Linux Kernel patch sumbittal checklist
> +Linux Kernel patch submission checklist
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Here are some basic things that developers should do if they want to see their
> @@ -9,7 +9,6 @@ Documentation/SubmittingPatches and elsewhere regarding submitting Linux
> kernel patches.
>
>
> -
> 1: Builds cleanly with applicable or modified CONFIG options =y, =m, and
> =n. No gcc warnings/errors, no linker warnings/errors.
>
>
>
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-06-06 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:55 Jesper Juhl
2007-06-06 15:31 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070606083145.0ed8b1ab.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®