From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
rth@twiddle.net, bryan.wu@analog.com, dhowells@redhat.com,
gerg@uclinux.org, lethal@linux-sh.org, wli@holomorphy.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu,
torvalds@linux-foundation.org
Subject: Re: [RFC][PATCH 2/2] xtime_lock vs update_process_times
Date: Mon, 28 Jan 2008 13:40:56 +0000 [thread overview]
Message-ID: <20080128134056.GA2792@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080128122030.GA14058@flint.arm.linux.org.uk>
On Mon, Jan 28, 2008 at 12:20:30PM +0000, Russell King wrote:
> On Mon, Jan 28, 2008 at 11:39:55AM +0100, Peter Zijlstra wrote:
> > move update_process_times() out from under xtime_lock.
> >
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
>
> Peter,
>
> Mind if I merge:
>
> > arch/arm/common/time-acorn.c | 2 --
> > arch/arm/mach-at91/at91sam926x_time.c | 3 ---
> > arch/arm/plat-iop/time.c | 4 ----
> > arch/arm/plat-s3c24xx/time.c | 2 --
>
> with my patch and submit it as part of the ARM merge (which I'm hoping
> to send in about an hours time.)
Don't bother - I'm sending my patch _now_ - I've run out of time to
merge the above into this ARM tree pull (since I want to get Linus to
pull it before yet more breakage happens to it - I've had to drop a
number of branches with new conflicts as of last night to even get this
far...)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-01-28 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:39 [RFC][PATCH 0/2] hrtimer breakage Peter Zijlstra
2008-01-28 10:39 ` [RFC][PATCH 1/2] Fix many ARM timer handlers Peter Zijlstra
2008-01-28 10:39 ` [RFC][PATCH 2/2] xtime_lock vs update_process_times Peter Zijlstra
2008-01-28 12:20 ` Russell King
2008-01-28 12:29 ` Peter Zijlstra
2008-01-28 13:40 ` Russell King [this message]
2008-02-04 1:29 ` Greg Ungerer
2008-02-13 21:18 ` Ivan Kokshaysky
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=20080128134056.GA2792@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=bryan.wu@analog.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rth@twiddle.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=wli@holomorphy.com \
/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.