public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: pull request for range-hrtimer updates
Date: Thu, 9 Oct 2008 14:33:45 +0200	[thread overview]
Message-ID: <20081009123345.GC2952@elte.hu> (raw)
In-Reply-To: <20081008083320.41840108@infradead.org>


* Arjan van de Ven <arjan@infradead.org> wrote:

> Hi,
> 
> a few changes have been put into the range-hrtimer tree; the first three have been on lkml before, 
> the last 2 are build fixes reported in the last few days.... please pull.
> 
> The following changes since commit a7cda5d3ae218476927ac3fd9756ea617c4ddfb2:
>   Ingo Molnar (1):
>         Merge branch 'sched/core'
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/arjan/linux-2.6-hrtimer.git master
> 
> Arjan van de Ven (5):
>       hrtimer: make the nanosleep() syscall use the per process slack
>       hrtimer: make the futex() system call use the per process slack value
>       hrtimer: peek at the timer queue just before going idle
>       select: fix alpha OSF wrapper
>       rangetimer: fix x86 build failure for the !HRTIMERS case
> 
>  arch/alpha/kernel/osf_sys.c |   13 +++++++------
>  drivers/cpuidle/cpuidle.c   |    7 +++++++
>  include/linux/hrtimer.h     |    7 +++++++
>  kernel/futex.c              |    6 +++++-
>  kernel/hrtimer.c            |   37 ++++++++++++++++++++++++++++++++++++-
>  5 files changed, 62 insertions(+), 8 deletions(-)

pulled into tip/timers/range-hrtimers, thanks Arjan!

	Ingo

  reply	other threads:[~2008-10-09 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 15:33 pull request for range-hrtimer updates Arjan van de Ven
2008-10-09 12:33 ` Ingo Molnar [this message]
     [not found]   ` <20081010113749.GA21937@elte.hu>
2008-10-12 23:37     ` Arjan van de Ven

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=20081009123345.GC2952@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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