From: Thomas Gleixner <tglx@linutronix.de>
To: Phil Carmody <ext-phil.2.carmody@nokia.com>
Cc: "arjan@linux.intel.com" <arjan@linux.intel.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Bityutskiy Artem (Nokia-MS/Helsinki)"
<Artem.Bityutskiy@nokia.com>
Subject: Re: timer: permit statically-declared work with deferrable timers
Date: Thu, 30 Sep 2010 22:55:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1009302255210.2416@localhost6.localdomain6> (raw)
In-Reply-To: <20100930205057.GC13742@esdhcp04044.research.nokia.com>
On Thu, 30 Sep 2010, Phil Carmody wrote:
> On 30/09/10 22:08 +0200, ext Thomas Gleixner wrote:
> > On Thu, 30 Sep 2010, Phil Carmody wrote:
> >
> > >
> > > Arjen, Thomas,
> > >
> > > This patch is an enabler which hopefully can lead to simplification of code
> > > elsewhere. For example, it would turn Artem's patch I refer to in the commit
> > > message (8eab945c5616fc984e97b922d6a2559be93f39a1) into just:
> > >
> > > -static DECLARE_DELAYED_WORK(cache_cleaner, do_cache_clean);
> > > +static DECLARE_DEFERRED_WORK(cache_cleaner, do_cache_clean);
> > >
> > > rather than the creation of a __init helper that required touching 3 files.
> > >
> > > I'm prepared to follow up with such simplifying patches if it's considered
> > > worthwhile.
> >
> > If it simplies stuff, no objections from my side. The patch looks
> > reasonable enough.
> >
> > How many (ab)users will it clean up ?
>
> Not a large number; absolute tops - a dozen. I've not investigated any apart from
> the couple that Artem addressed initially.
>
> And it's OK, the clients weren't the _ab_users. If anything we're the abusers for
> using sleight-of-hand to hide flags inside pointer values. (Which the C standard
> and GCC tried hard to stop us doing. Not hard enough, though ;-) .)
>
> My main intention is to make future patches like Artem's trivial. Change the
> type - change one line. Life's too short to headscratch and fight compilers.
Fair enough.
tglx
prev parent reply other threads:[~2010-09-30 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 19:26 Phil Carmody
2010-09-30 19:26 ` [PATCH 1/1] " Phil Carmody
2010-10-01 6:19 ` Artem Bityutskiy
2010-09-30 20:08 ` Thomas Gleixner
2010-09-30 20:50 ` Phil Carmody
2010-09-30 20:55 ` Thomas Gleixner [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=alpine.LFD.2.00.1009302255210.2416@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=Artem.Bityutskiy@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=ext-phil.2.carmody@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®