public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: eranian@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH] add i386 idle notifier (take 3)
Date: Wed, 20 Dec 2006 21:05:14 -0800	[thread overview]
Message-ID: <20061220210514.42ed08cc.akpm@osdl.org> (raw)
In-Reply-To: <20061220140500.GB30752@frankl.hpl.hp.com>

On Wed, 20 Dec 2006 06:05:00 -0800
Stephane Eranian <eranian@hpl.hp.com> wrote:

> Hello,
> 
> Here is the latest version of the idle notifier for i386.
> This patch is against 2.6.20-rc1 (GIT). In this kernel, the idle
> loop code was modified such that the lowest level idle
> routines do not have loops anymore (e.g., poll_idle). As such,
> we do not need to call enter_idle() in all the interrupt handlers.
> 
> This patch also duplicates the x86-64 bug fix for a race condition
> as posted by Venkatesh Pallipadi from Intel.
> 
> changelog:
> 	- add idle notification mechanism to i386
> 

None of the above text is actually usable as a changelog entry.  We are
left wondering:

- why is this patch needed?

- what does it do?

- how does it do it?

The three questions which all changelogs should answer ;)

  reply	other threads:[~2006-12-21  5:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 14:05 [PATCH] add i386 idle notifier (take 3) Stephane Eranian
2006-12-21  5:05 ` Andrew Morton [this message]
2006-12-21  9:12   ` Stephane Eranian
2006-12-22  1:06     ` Adrian Bunk
2006-12-22 10:07       ` Stephane Eranian
2006-12-23 11:40         ` Adrian Bunk
2007-01-03 13:20           ` Stephane Eranian
2007-01-03 23:07             ` Adrian Bunk
2007-01-05 10:55               ` Stephane Eranian
2007-01-05 13:36                 ` Adrian Bunk
2007-01-09 10:49                   ` Stephane Eranian

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=20061220210514.42ed08cc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --cc=eranian@hpl.hp.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