From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: Martin Waitz <tali@admingilde.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][kernel-doc] Add DocBook documentation for workqueue functions
Date: Thu, 20 Jul 2006 13:49:25 +0200 [thread overview]
Message-ID: <44BF6DC5.4030708@s5r6.in-berlin.de> (raw)
In-Reply-To: <200607201145.19147.eike-kernel@sf-tec.de>
Rolf Eike Beer wrote:
[...]
> int fastcall schedule_work(struct work_struct *work)
> {
> return queue_work(keventd_wq, work);
> }
> EXPORT_SYMBOL(schedule_work);
>
> +/**
> + * schedule_work - put work task in global workqueue after delay
This should read "schedule_delayed_work".
> + *
> + * @work: job to be done
> + * @delay: number of jiffies to wait
> + *
> + * After waiting for a given time this puts a job in the kernel-global
> + * workqueue.
> + */
> int fastcall schedule_delayed_work(struct work_struct *work, unsigned long delay)
> {
> return queue_delayed_work(keventd_wq, work, delay);
> }
> EXPORT_SYMBOL(schedule_delayed_work);
>
> +/**
> + * schedule_work - queue work in global workqueue on specific CPU after delay
"schedule_delayed_work_on"
> + *
> + * @cpu: cpu to use
> + * @work: job to be done
> + * @delay: number of jiffies to wait
> + *
> + * After waiting for a given time this puts a job in the kernel-global
> + * workqueue.
> + */
> int schedule_delayed_work_on(int cpu,
> struct work_struct *work, unsigned long delay)
> {
--
Stefan Richter
-=====-=-==- -=== =--==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-07-20 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 9:45 Rolf Eike Beer
2006-07-20 11:49 ` Stefan Richter [this message]
2006-07-20 12:22 ` Rolf Eike Beer
2006-07-20 12:52 ` Randy.Dunlap
2006-07-20 13:03 ` Rolf Eike Beer
2006-07-20 13:11 ` Rolf Eike Beer
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=44BF6DC5.4030708@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@osdl.org \
--cc=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tali@admingilde.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
Powered by JetHome