All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Veen <arjan@infradead.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jon Masters <jonathan@jonmasters.org>,
	Sven Dietrich <sdietrich@suse.de>
Subject: Re: [RFC patch 0/5] genirq: add infrastructure for threaded interrupt handlers
Date: Fri, 03 Oct 2008 07:44:13 -0700	[thread overview]
Message-ID: <1223045053.2995.251.camel@laptop-eth> (raw)
In-Reply-To: <alpine.LFD.1.10.0810030215190.5549@apollo.tec.linutronix.de>

On Fri, 2008-10-03 at 02:26 +0200, Thomas Gleixner wrote:
> On Thu, 2 Oct 2008, Daniel Walker wrote:
> > On Thu, 2008-10-02 at 18:28 -0400, Steven Rostedt wrote:
> > > > > Why are you bringing up real time in this thread?? The thread has
> > > > > absolutely nothing to do with real time. This thread is about a better
> > > > > way to handle interrupt handlers.
> > > > 
> > > > I'm concerned about the connection between the two, which is what I'm
> > > > commenting on.
> > > 
> > > Well, please take that up separately. Do you see these patches going
> > > into the -rt tree?  No, they are going in mainline. We will deal with
> > > them for -rt when the time comes.
> > 
> > It's an RFC after all, it's not going into anything at this point..
> 
> Because you are deciding what's going into mainline, right ?

You flagged this as an RFC, typically that means it's a work in
progress .. Usually a work in progress does go into mainline.

> > > You are bringing up concerns about mainline changes with something that
> > > is maintained outside the mainline tree.  Changes to mainline have never
> > > been influenced by changes maintained outside of mainline.
> > 
> > Again it's an RFC .. It's not going into mainline.. 
> 
> You made such a statement vs. hrtimers some time ago. 

hrtimers didn't go RFC then straight to mainline either.

> > > Yes Daniel, I know. But this is not a conversation. This is a email thread
> > > that is talking about changes to mainline. The mainline kernel developers
> > > really don't care about any issues that these changes will do to the
> > > real time project. The real time project is a niche, and is currently
> > > outside the mainline tree. Hence, lets stop bothering mainline 
> > > developers with our issues.
> > 
> > Your speaking for a lot of developers.. It's an RFC, it's coming from
> > real time developers, it's real time connected, and this is the real
> > time development list ..
> 
> This RFC patch is from a mainline developer/ maintainer who happens to
> be a real time developer as well.

And is submitting a real time core features.

> Welcome to my real time incoherent nonsense filter

You ask for comments, than get upset when you get some .. If anyone
needs to be filtered it's you.

Daniel


  reply	other threads:[~2008-10-03 14:44 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 23:02 [RFC patch 0/5] genirq: add infrastructure for threaded interrupt handlers Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 1/5] genirq: make irqreturn_t an enum Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 2/5] genirq: add a quick check handler Thomas Gleixner
2008-10-02  0:47   ` Jon Masters
2008-10-02  5:09     ` Steven Rostedt
2008-10-02 10:51       ` Jon Masters
2008-10-02 22:06         ` Greg KH
2008-10-02  4:52   ` Steven Rostedt
2008-10-03  8:29   ` Christoph Hellwig
2008-10-03 10:37     ` Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 3/5] genirq: add threaded interrupt handler support Thomas Gleixner
2008-10-02  5:01   ` Steven Rostedt
2008-10-01 23:02 ` [RFC patch 4/5] genirq: add a helper to check whether the irq thread should run Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 5/5] genirq: make irq threading robust Thomas Gleixner
2008-10-02  0:52   ` Jon Masters
2008-10-02  5:20     ` Steven Rostedt
2008-10-01 23:23 ` [RFC patch 0/5] genirq: add infrastructure for threaded interrupt handlers Andrew Morton
2008-10-01 23:29   ` Arjan van de Ven
2008-10-01 23:40     ` Andrew Morton
2008-10-01 23:58       ` Thomas Gleixner
2008-10-02  0:40 ` Jon Masters
2008-10-02 22:07   ` Greg KH
2008-10-08 22:18     ` Ingo Oeser
2008-10-02  1:53 ` Daniel Walker
2008-10-02 15:02   ` Steven Rostedt
2008-10-02 15:48     ` Daniel Walker
2008-10-02 18:42       ` Thomas Gleixner
2008-10-02 19:04         ` Daniel Walker
2008-10-02 19:23           ` Steven Rostedt
2008-10-02 19:28           ` Ingo Molnar
2008-10-02 20:09             ` Daniel Walker
2008-10-02 20:14               ` Steven Rostedt
2008-10-02 20:48                 ` Daniel Walker
2008-10-02 21:05                   ` Steven Rostedt
2008-10-02 21:30                     ` Daniel Walker
2008-10-02 22:28                       ` Steven Rostedt
2008-10-02 23:24                         ` Daniel Walker
2008-10-03  0:26                           ` Thomas Gleixner
2008-10-03 14:44                             ` Daniel Walker [this message]
2008-10-02 14:46 ` Andi Kleen
2008-10-02 21:31   ` Greg KH
2008-10-02 22:33     ` Arjan van de Ven
2008-10-03  3:25       ` Andi Kleen
2008-10-03  3:48         ` Arjan van de Ven
2008-10-03  4:35           ` Andi Kleen
2008-10-03  3:23     ` Andi Kleen
2008-10-21  1:32 ` [RFC patch] genirq threading for ehci, ohci and uhci USB hosts Sven-Thorsten Dietrich
2008-10-21  1:32   ` Sven-Thorsten Dietrich
2008-10-21  2:07   ` Jonathan Woithe
2008-10-21 10:29     ` [RFC patch] genirq threading (v2) for ehci, ohci and uhci USB hosts and ohci1394 Sven-Thorsten Dietrich

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=1223045053.2995.251.camel@laptop-eth \
    --to=dwalker@mvista.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=sdietrich@suse.de \
    --cc=tglx@linutronix.de \
    --cc=torvalds@osdl.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 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.