From: root@smtp.nexlab.net
To: undisclosed-recipients:;
Date: Tue, 24 May 2005 11:17:50 +0200 (CEST) [thread overview]
Message-ID: <20050524091750.75FDFFA3F@smtp.nexlab.net> (raw)
by smtp.nexlab.net (Postfix) with ESMTP id BE232FB71
for <chiakotay@nexlab.it>; Tue, 24 May 2005 10:01:45 +0200 (CEST)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S261355AbVEXGwi (ORCPT <rfc822;chiakotay@nexlab.it>);
Tue, 24 May 2005 02:52:38 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261357AbVEXGwi
(ORCPT <rfc822;linux-kernel-outgoing>);
Tue, 24 May 2005 02:52:38 -0400
Received: from mx2.elte.hu ([157.181.151.9]:24245 "EHLO mx2.elte.hu")
by vger.kernel.org with ESMTP id S261355AbVEXGwe (ORCPT
<rfc822;linux-kernel@vger.kernel.org>);
Tue, 24 May 2005 02:52:34 -0400
Received: from chiara.elte.hu (chiara.elte.hu [157.181.150.200])
by mx2.elte.hu (Postfix) with ESMTP id D26D231CA62;
Tue, 24 May 2005 08:43:21 +0200 (CEST)
Received: by chiara.elte.hu (Postfix, from userid 17806)
id 63EF71FC2; Tue, 24 May 2005 08:45:33 +0200 (CEST)
Date: Tue, 24 May 2005 08:45:22 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@infradead.org>,
Daniel Walker <dwalker@mvista.com>, linux-kernel@vger.kernel.org,
akpm@osdl.org, sdietrich@mvista.com
Subject: Re: RT patch acceptance
Message-ID: <20050524064522.GA9385@elte.hu>
References: <1116890066.13086.61.camel@dhcp153.mvista.com> <20050524054722.GA6160@infradead.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050524054722.GA6160@infradead.org>
User-Agent: Mutt/1.4.2.1i
X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73
X-ELTE-VirusStatus: clean
X-ELTE-SpamCheck: no
X-ELTE-SpamCheck-Details: score=-4.9, required 5.9,
BAYES_00 -4.90
X-ELTE-SpamLevel:
X-ELTE-SpamScore: -4
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
* Christoph Hellwig <hch@infradead.org> wrote:
> Personally I think interrupt threads, spinlocks as sleeping mutexes
> and PI is something we should keep out of the kernel tree. [...]
it's not really a problem - they integrate nicely. They also found
dozens of hard-to-catch bugs already so if you dont care about embedded
systems at all then worst-case you can consider it a spinlock debugging
mechanism, with the difference that DEBUG_SPINLOCK is far uglier ;)
Anyway, this discussion is premature, as i'm not submitting all these
patches yet.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2005-05-24 9:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050524091750.75FDFFA3F@smtp.nexlab.net \
--to=root@smtp.nexlab.net \
/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®