From: Ingo Molnar <mingo@elte.hu>
To: Frank Rowand <frowand@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] ppc RT: Realtime preempt support for PPC
Date: Wed, 16 Mar 2005 11:09:14 +0100 [thread overview]
Message-ID: <20050316100914.GA16012@elte.hu> (raw)
In-Reply-To: <422CCC1D.1050902@mvista.com>
hi Frank - sorry about the late reply, was busy with other things. Your
ppc patches look mostly mergeable, with some small details still open:
* Frank Rowand <frowand@mvista.com> wrote:
> The patches are:
>
> 1/5 ppc_rt.patch - the core realtime functionality for PPC
what is the rationale behind the rt_lock.h changes? The #ifdef
CONFIG_PPC32 changes in generic code are not really acceptable, the -RT
tree tries to keep a single spinlock definition and debugging
primitives, across all architectures.
to drive things forward, i've applied the first 3 patches (except the
rt_lock.h chunk from the first patch), and released it as part of the
40-03 patch:
http://redhat.com/~mingo/realtime-preempt/
so that you can send followup patches based on this. Patches #4 and #5
are routed via the upstream PPC tree, so -RT should not carry them,
right?
Ingo
next prev parent reply other threads:[~2005-03-16 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 21:48 [PATCH 0/5] ppc RT: Realtime preempt support for PPC Frank Rowand
2005-03-16 10:09 ` Ingo Molnar [this message]
2005-03-16 15:30 ` K.R. Foley
2005-03-17 8:38 ` Ingo Molnar
2005-03-22 0:38 ` Frank Rowand
2005-03-31 1:36 ` Frank Rowand
2005-03-31 9:16 ` Ingo Molnar
2005-04-01 23:55 ` Frank Rowand
2005-04-05 5:39 ` Ingo Molnar
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=20050316100914.GA16012@elte.hu \
--to=mingo@elte.hu \
--cc=frowand@mvista.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