From: Jeff Garzik <jgarzik@pobox.com>
To: Henne <henne@nachtwindheim.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ata-piix: kerneldoc-error-on-ata_piixc.patch 2nd try
Date: Mon, 25 Sep 2006 15:39:08 -0400 [thread overview]
Message-ID: <4518305C.3090906@pobox.com> (raw)
In-Reply-To: <451826BE.2040201@nachtwindheim.de>
Henne wrote:
> Heres a new version of the kerneldoc error in ata_piix.c
> The old one which doesn't apply clean is in 2.6.18-mm1 and can be removed there if acked.
>
> Greets,
> Henne
>
> From: Henrik Kretzschmar <henne@nachtwindheim.de>
>
> Fixes an error in kerneldoc of ata_piix.c.
> This is the 2nd try, written for 2.6.18-git4
> Signed-off-by: Henrik Kretzschmar <henne@nachtwindheim.de>
Several problems with your patch format:
1) your subject line includes-a-bunch-of-words-separated-by-dashes,
which is incorrect. Just use standard English.
2) "2nd try" should be inside the brackets ("[", "]"), so that the
script removes it during merge
3) All comments such as the first paragraph and "Greets, Henne" should
be moved underneath the "---" separator, so that they are not copied
into the kernel changelog verbatim. You force people to hand-edit your
email before merging.
4) No need for "From:" in the email body, it duplicates the email's
RFC822 From header.
5) Another comment "This is the 2nd try, written for 2.6.18-git4" which
should be moved after the "---" separator. Otherwise, it must be
hand-edited out.
next prev parent reply other threads:[~2006-09-25 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 18:58 [PATCH] ata-piix: kerneldoc-error-on-ata_piixc.patch 2nd try Henne
2006-09-25 19:39 ` Jeff Garzik [this message]
2006-09-25 20:11 ` Randy Dunlap
2006-09-25 20:13 ` Jeff Garzik
2006-09-25 20:37 ` Henne
2006-09-25 21:23 ` Randy Dunlap
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=4518305C.3090906@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=henne@nachtwindheim.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.