public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Sven-Thorsten Dietrich <sven@thebigcorporation.com>,
	Remy Bohmer <linux@bohmer.net>,
	LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>,
	Jon Masters <jonathan@jonmasters.org>
Subject: Re: Preempt-RT patch for 2.6.25
Date: Mon, 05 May 2008 18:43:04 -0700	[thread overview]
Message-ID: <1210038184.17132.100.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.10.0805060258360.3318@apollo.tec.linutronix.de>


On Tue, 2008-05-06 at 03:30 +0200, Thomas Gleixner wrote:
> On Mon, 5 May 2008, Daniel Walker wrote:
> > On Tue, 2008-05-06 at 01:47 +0200, Ingo Molnar wrote:
> > > * Daniel Walker <dwalker@mvista.com> wrote:
> > > 
> > > > I think dropping ports (temporarily) is perfectly reasonable. There is 
> > > > no reason to hamper forward development just to keep old architecture 
> > > > ports in the tree.
> > > 
> > > You are missing the point: a lot of people (those who wrote the brunt of 
> > > the -rt tree and who maintained it over the years and who maintain it 
> > > today) think it's not reasonable and have stated it very clearly to you 
> > > that it's a bug. Keeping things alive is not preventing forward 
> > > development.
> > 
> > That has always been my intention. I've never said the arch code would
> > be permanently gone. 
> 
> Get it. Dropping it means bitrot.
> 
> The responsible maintainers keep that (maybe stale) code at least in
> sync as far as the obvious fixups are concerned.
> 
> Your way of chosing the least effort approach and justifying it with
> handwaving arguments is just disgusting.

Can you stop with these comments. Lets try to resolve this in civil way.

Daniel


  reply	other threads:[~2008-05-06  1:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 18:02 Preempt-RT patch for 2.6.25 Remy Bohmer
2008-05-02 18:34 ` Sven-Thorsten Dietrich
2008-05-02 18:45   ` Steven Rostedt
2008-05-02 18:54     ` Sven-Thorsten Dietrich
2008-05-02 19:02       ` Steven Rostedt
2008-05-02 19:14         ` Sven-Thorsten Dietrich
2008-05-03  2:44           ` Steven Rostedt
2008-05-05 14:21             ` Daniel Walker
2008-05-05 16:01         ` Daniel Walker
2008-05-05 16:11           ` Steven Rostedt
2008-05-05 16:19             ` Daniel Walker
2008-05-05 16:44               ` Steven Rostedt
2008-05-05 17:04                 ` Daniel Walker
2008-05-05 18:32                   ` Steven Rostedt
2008-05-05 18:58                     ` Daniel Walker
2008-05-05 21:01                       ` Thomas Gleixner
2008-05-05 22:12                         ` Daniel Walker
2008-05-05 23:47                           ` Ingo Molnar
2008-05-06  0:11                             ` Daniel Walker
2008-05-06  1:30                               ` Thomas Gleixner
2008-05-06  1:43                                 ` Daniel Walker [this message]
2008-05-06  8:43                               ` Ingo Molnar
2008-05-06 16:01                                 ` Daniel Walker
2008-05-06  0:13                           ` Thomas Gleixner
2008-05-06  1:54                           ` Thomas Gleixner
2008-05-06  2:10                             ` Daniel Walker
2008-05-06  8:19                               ` Thomas Gleixner
2008-05-06 10:40                           ` Steven Rostedt
2008-05-06 16:05                             ` Daniel Walker
2008-05-06 16:32                               ` Steven Rostedt
2008-05-06 17:06                                 ` Daniel Walker
2008-05-06 20:59                                   ` Steven Rostedt
2008-05-05 16:17     ` Daniel Walker
2008-05-05 16:21       ` Steven Rostedt
2008-05-05 16:31         ` Daniel Walker

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=1210038184.17132.100.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux@bohmer.net \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=sven@thebigcorporation.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox