From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Kevin Diggs <kevdig@hypersurf.com>
Subject: Re: Corrections please ...
Date: Tue, 19 Aug 2008 11:02:53 +0200 [thread overview]
Message-ID: <200808191102.53911.arnd@arndb.de> (raw)
In-Reply-To: <48A9E2C6.1030205@hypersurf.com>
On Monday 18 August 2008, Kevin Diggs wrote:
> Subject: Corrections please ...
The subject should be the one line change log, e.g.
[PATCH] add kerneldoc comments for completion.h
Also, cc the maintainer of the code. If you can't tell
from the MAINTAINERS file, look for the most common
name when doing 'git log path/to/file.c'. In this case,
there does not seem to be an actual maintainer, but I
would expect Willy and Ingo to be interested in the code.
Read Documentation/SubmittingPatches.
> Could I get any needed corrections on this. Especially on the "???"
>
The introductory text should explain why the patch is needed.
If you have more comments, put them behind the changelog text,
under a '---' line.
> [kevdig@PowerMac8600B linux-2.6.26]$ diff -U3
> include/linux/completion.{h.orig,h}|more
> --- include/linux/completion.h.orig 2008-08-13 00:56:52.000000000 -0700
> +++ include/linux/completion.h 2008-08-18 13:00:23.000000000 -0700
Patches should be in -p1 format. Best use a tool like quilt, git or
mercurial to generate the patch instead of doing it by hand.
> @@ -10,6 +10,16 @@
>
> #include <linux/wait.h>
>
> +/**
> + * struct completion - structure used to maintain state for a "completion"
> + * @done: counting variable used to signal completion
> + * @wait: internal wait queue head; used for locking and synchronization
> + *
> + * This is the structure used to maintain the state for a "completion". See
> + * also: complete(), wait_for_completion() (and friends _timeout,
> + * _interruptible, _interruptible_timeout, and _killable),
> init_completion(),
> + * and macros DECLARE_COMPLETION() and INIT_COMPLETION().
> + */
Line wrapping is broken, you need the right settings for sending unmodified
emails from your mail client.
Arnd <><
prev parent reply other threads:[~2008-08-19 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 20:59 Corrections please Kevin Diggs
2008-08-19 1:02 ` Michael Ellerman
2008-08-19 9:02 ` Arnd Bergmann [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=200808191102.53911.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@ozlabs.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.