public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Phil Carmody <ext-phil.2.carmody@nokia.com>
Cc: "arjan@linux.intel.com" <arjan@linux.intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] timer: permit statically-declared work with deferrable timers
Date: Fri, 01 Oct 2010 09:19:33 +0300	[thread overview]
Message-ID: <1285913973.11684.63.camel@localhost> (raw)
In-Reply-To: <1285874789-1481-2-git-send-email-ext-phil.2.carmody@nokia.com>

On Thu, 2010-09-30 at 21:26 +0200, ext Phil Carmody wrote:
> Currently, you have to just define a delayed_work uninitialised, and then
> initialise it before first use. That's a tad clumsy. At risk of playing
> mind-games with the compiler, fooling it into doing pointer arithmetic
> with compile-time-constants, this lets clients properly initialise delayed
> work with deferrable timers statically.
> 
> This patch was inspired by the issues which lead Artem Bityutskiy
> to commit 8eab945c5616fc984e97b922d6a2559be93f39a1.
> 
> Signed-off-by: Phil Carmody <ext-phil.2.carmody@nokia.com>
Acked-by: Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)


  reply	other threads:[~2010-10-01  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 19:26 timer: permit statically-declared work with deferrable timers Phil Carmody
2010-09-30 19:26 ` [PATCH 1/1] " Phil Carmody
2010-10-01  6:19   ` Artem Bityutskiy [this message]
2010-09-30 20:08 ` Thomas Gleixner
2010-09-30 20:50   ` Phil Carmody
2010-09-30 20:55     ` Thomas Gleixner

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=1285913973.11684.63.camel@localhost \
    --to=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 \
    --cc=tglx@linutronix.de \
    /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