From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
torvalds@linux-foundation.org, zippel@linux-m68k.org,
schwab@suse.de, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Make the kernel NTP code hand 64-bit *unsigned* values to do_div() [try #3]
Date: Sat, 23 Feb 2008 23:05:22 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802232302110.7583@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080223130743.02caa1ab.akpm@linux-foundation.org>
On Sat, 23 Feb 2008, Andrew Morton wrote:
> > > Thomas, do you consider ntp to fall under git-hrt?
> >
> > I'll pick it up.
> >
> OK. And this is still
> git+ssh://master.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-hrt.git#mm,
> yes?
Yes
> Can we please define the scope of that tree?
Primary scope is hrtimer, posixtimer, clockevents & Co.
In the last month I fed a lot of timekeeping/ntp stuff via -hrt as
well. If there is no objection, I'm happy to provide the sink for
those.
> Please review
>
> fix-shadowed-variables-in-kernel-posix-cpu-timersc.patch
> timers-simplify-lockdep-stuff.patch
> hrtimers-simplify-lockdep-stuff.patch
> kill-double_spin_lock.patch
> ntp-make-the-kernel-ntp-code-hand-64-bit-unsigned-values-to-do_div.patch
>
> from http://userweb.kernel.org/~akpm/mmotm/broken-out/. I think they're
> all probably git-hrt material.
Will do tomorrow, when I'm more awake.
> Can we get that tree into linux-next too please?
Will contact Stephen.
Thanks,
tglx
prev parent reply other threads:[~2008-02-23 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 16:50 [PATCH] Make the kernel NTP code hand 64-bit *unsigned* values to do_div() [try #3] David Howells
2008-02-23 8:04 ` Andrew Morton
2008-02-23 21:01 ` Thomas Gleixner
2008-02-23 21:07 ` Andrew Morton
2008-02-23 22:05 ` 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.1.00.0802232302110.7583@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwab@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.