From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
RT-Users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: v2.6.23-rc4-rt1 / new project URL
Date: Mon, 10 Sep 2007 18:15:02 +0200 [thread overview]
Message-ID: <1189440902.21778.18.camel@twins> (raw)
In-Reply-To: <1189437492.14752.1.camel@imap.mvista.com>
On Mon, 2007-09-10 at 08:18 -0700, Daniel Walker wrote:
> On Mon, 2007-09-10 at 14:35 +0200, Peter Zijlstra wrote:
>
> > > - simple_irq change (Kevin Hilman): needs more thought
> > > - RCU updates (Paul McKenney): needs proper integration
> > > - latency tracer changes (Daniel Walker): needs review
> > > - PICK_OP changes (Daniel Walker): needs review
> >
> > This one seems to have slipped through the cracks:
> > http://lkml.org/lkml/2007/8/16/135
>
> There was a comment in this patch that reads,
>
> + /*
> + * all modifications are done under spinlocks
> + * but this read is not, the unlock acks as a wmb
> + * for modifications.
> + */
>
> I you mean "acts" (like an actor) instead of "acks" here right?
ah, indeed :-) sometimes my fingers have a life of their own.
next prev parent reply other threads:[~2007-09-10 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 20:59 v2.6.23-rc4-rt1 / new project URL Thomas Gleixner
2007-09-01 0:01 ` Daniel Walker
2007-09-01 7:27 ` Thomas Gleixner
2007-09-01 14:25 ` Daniel Walker
2007-09-03 1:16 ` Steven Rostedt
2007-09-01 15:50 ` Daniel Walker
2007-09-03 7:13 ` [LOCKDEP] v2.6.23-rc4-rt1 Sven-Thorsten Dietrich
2007-09-03 10:43 ` v2.6.23-rc4-rt1 / new project URL John Sigler
2007-09-06 13:00 ` Alessio Igor Bogani
2007-09-10 12:35 ` Peter Zijlstra
2007-09-10 15:18 ` Daniel Walker
2007-09-10 16:15 ` Peter Zijlstra [this message]
2007-09-26 21:16 ` Peter Zijlstra
2007-09-26 21:27 ` Steven Rostedt
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=1189440902.21778.18.camel@twins \
--to=peterz@infradead.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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 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.