From: Andrew Morton <akpm@osdl.org>
To: davem@davemloft.net, netdev@oss.sgi.com, arjan@infradead.org
Subject: Re: [patch 1/2] cancel_rearming_delayed_work()
Date: Sun, 30 Jan 2005 22:41:49 -0800 [thread overview]
Message-ID: <20050130224149.29bb18a0.akpm@osdl.org> (raw)
In-Reply-To: <200501310633.j0V6X0l01364@mail.osdl.org>
akpm@osdl.org wrote:
>
> Add library functions to reliably kill off a delayed work whose handler
> re-adds the delayed work. One for keventd, one for caller-owned workqueues.
> DESC
> make cancel_rearming_delayed_workqueue static
> EDESC
> From: Arjan van de Ven <arjan@infradead.org>
>
> cancel_rearming_delayed_workqueue() is only used inside workqueue.c; make
> this function static (the more useful wrapper around it later in that
> function remains non-static and exported)
hmm, actually, had I paid any attention to Arjan's patch I'd have dropped it ;)
cancel_rearming_delayed_workqueue() make sense and should be part of the
workqueue API, even if nothing uses it yet.
Whatever - we can fix that up sometime.
prev parent reply other threads:[~2005-01-31 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 6:33 [patch 1/2] cancel_rearming_delayed_work() akpm
2005-01-31 6:41 ` Andrew Morton [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=20050130224149.29bb18a0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).