From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Kevin Diggs <kevdig@hypersurf.com>
Cc: linux-kernel@vger.kernel.org, Dave Chinner <david@fromorbit.com>
Subject: Re: [Fwd: Corrections please ...]
Date: Tue, 19 Aug 2008 14:03:31 +0200 [thread overview]
Message-ID: <48AAB693.8080906@s5r6.in-berlin.de> (raw)
In-Reply-To: <48AA7F47.5050805@hypersurf.com>
Kevin Diggs wrote:
> Files attached this time ...
Alas several MUAs don't quote attachments in replies. Hence the optimum
would be if you use a MUA which allows to insert text files without
whitespace change.
Also, when you respond on LKML, always use "reply to all" to keep
previous responders in a thread Cc'd. This is necessary due to the high
volume of LKML, and in order to not force people to subscribe to LKML.
> --- 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
> @@ -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().
> + */
> struct completion {
> unsigned int done;
> wait_queue_head_t wait;
.done and .wait are not public AFAIU and should therefore not be
documented as an API.
> @@ -36,6 +46,13 @@
> # define DECLARE_COMPLETION_ONSTACK(work) DECLARE_COMPLETION(work)
> #endif
>
> +/**
> + * init_completion: - Initialize a dynamically allocated completion
> + * @x: completion structure that is to be initialized
> + *
> + * This inline function will initialize a dynamically created completion
> + * structure.
> + */
> static inline void init_completion(struct completion *x)
> {
> x->done = 0;
The last sentence is redundant and should be omitted.
--
Stefan Richter
-=====-==--- =--- =--==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-08-19 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 1:53 [Fwd: Corrections please ...] Kevin Diggs
2008-08-19 2:41 ` Dave Chinner
2008-08-19 8:07 ` Kevin Diggs
2008-08-19 12:03 ` Stefan Richter [this message]
2008-08-19 16:15 ` Marcin Slusarz
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=48AAB693.8080906@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=david@fromorbit.com \
--cc=kevdig@hypersurf.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox