From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [announce] split-up -rt patch-queue, v2.6.22.1-rt2
Date: Thu, 12 Jul 2007 19:01:29 +0200 [thread overview]
Message-ID: <1184259689.12353.236.camel@chaos> (raw)
In-Reply-To: <1184257998.7974.44.camel@dhcp193.mvista.com>
Daniel,
On Thu, 2007-07-12 at 09:33 -0700, Daniel Walker wrote:
> On Thu, 2007-07-12 at 17:37 +0200, Ingo Molnar wrote:
> > We are pleased to announce something we've been working on for some
> > time: a finegrained, split-up patch queue of the -rt kernel patch. From
> > now on (as of 2.6.22.1-rt2) it will be part of every upstream -rt
> > release and it is available from the -rt download site:
> >
> > http://redhat.com/~mingo/realtime-preempt/
> >
> > the -rt patch-queue consists of 374 patches at the moment, which do:
> >
> > 698 files changed, 27920 insertions(+), 9603 deletions(-)
>
> Is the number of patches relevant to you ? It seems like some patches
> could be boken out more. For instance there could be a per-architecture
> patch dedicated to converting spinlocks to raw spinlocks .. I was
> looking at preempt-realtime-i386.patch ..
We know very well and Ingo nowhere said, that this is not a perfect
queue, but it was and still is _our_ work base and we opened it up for
the reasons explained.
What we definitely not need is platitude advise, how we should manage
the queue and what could be improved as well as hysteric shuffling in
the queue right now.
There are enough problems to work on, cleanups to do and the least one
is to worry about how the queue is organized.
tglx
next prev parent reply other threads:[~2007-07-12 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 15:37 Ingo Molnar
2007-07-12 15:40 ` Daniel Walker
2007-07-12 16:33 ` Daniel Walker
2007-07-12 17:01 ` Thomas Gleixner [this message]
2007-07-12 17:02 ` Daniel Walker
2007-07-12 18:40 ` Thomas Gleixner
2007-07-12 19:37 ` Daniel Walker
2007-07-12 21:10 ` Serge Belyshev
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=1184259689.12353.236.camel@chaos \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®