public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Scott Wood <scott@timesys.com>, Ingo Molnar <mingo@elte.hu>,
	"La Monte H.P. Yarroll" <piggy@timesys.com>,
	Manas Saksena <manas.saksena@timesys.com>,
	Philippe Gerum <rpm@xenomai.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] IRQ threads
Date: Wed, 28 Jul 2004 15:57:52 -0400	[thread overview]
Message-ID: <41080540.9040401@opersys.com> (raw)
In-Reply-To: <1091043218.766.10.camel@mindpipe>


Lee Revell wrote:
> I am familiar with Adeos, as well as other hard-RT solutions for Linux. 
> I did my homework before deciding that I do not in fact need hard-RT, so
> I really am not interested in your flamewars, keep them on your RT
> mailing lists.
> 
> The part that was obvious commercially motivated FUD (and which you
> omitted) t in which you badmouth TimeSys and its services, then  Your
> .sig states that you are a consultant specializing in realtime and
> embedded Linux.

And your point is ... ??? Should everyone on this list who's working for
a company that is involved in a certain speciality field stop commenting
on the solutions proposed by people working for other companies?

This style of attack is called sophism, and it is total crap for the
educated crowd. Attacking someone based on who he works for and what he
does has nothing to do with actually presenting a case against his
arguments.

The personal experiences I've stated before have happened. Lest you
suggest that those of us who have had bad experiences with certain
pieces of technology should shut-up and not voice our complaints for
fear of offending someone out there? Sorry, I don't live in Disneyland.

If you're not interested in hard-rt, that's you're business. Others
on this list have expressed interest in the past for this, and you
are welcome to ignore any traffic in this regard. For my part, I
will get involved whenever I see someone suggesting something that
relates to real-time because this is a topic I'm interested in.
What a surprise that I'm actually working in a field I'm interested
in ... sheesh ...

Karim
-- 
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546


  reply	other threads:[~2004-07-28 20:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 22:50 [patch] IRQ threads Scott Wood
2004-07-28  6:27 ` Ingo Molnar
2004-07-28 15:38   ` Karim Yaghmour
2004-07-28 16:01     ` Karim Yaghmour
2004-07-28 21:23   ` Bill Huey
2004-07-28 21:35     ` Scott Wood
2004-07-29 21:08       ` Bill Huey
2004-07-29 22:44       ` Ingo Molnar
2004-07-28 23:24   ` Scott Wood
2004-07-28  8:10 ` Ingo Molnar
2004-07-28 23:12   ` Scott Wood
2004-07-29 19:33     ` Ingo Molnar
2004-07-29 20:21       ` Scott Wood
2004-07-29 21:12         ` Alan Cox
2004-07-28 15:45 ` Karim Yaghmour
2004-07-28 18:28   ` Lee Revell
2004-07-28 19:12     ` Karim Yaghmour
2004-07-28 19:33       ` Lee Revell
2004-07-28 19:57         ` Karim Yaghmour [this message]
2004-07-28 20:35           ` Lee Revell
2004-07-28 21:15             ` Karim Yaghmour
2004-07-28 21:43               ` Lee Revell
2004-07-28 21:38                 ` Karim Yaghmour
2004-07-28 20:21         ` Bill Huey
2004-07-28 20:42           ` Lee Revell
2004-07-28 20:46             ` Bill Huey
2004-07-28 21:48           ` Karim Yaghmour
2004-07-28 22:30             ` Bill Huey
2004-07-28 22:03           ` Philippe Gerum
  -- strict thread matches above, loose matches on Subject: below --
2004-07-29 20:33 Albert Cahalan

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=41080540.9040401@opersys.com \
    --to=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manas.saksena@timesys.com \
    --cc=mingo@elte.hu \
    --cc=piggy@timesys.com \
    --cc=rlrevell@joe-job.com \
    --cc=rpm@xenomai.org \
    --cc=scott@timesys.com \
    /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