public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Altenberg <tb10alj@tglx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: karsten wiese <annabellesgarden@yahoo.de>,
	Rui Nuno Capela <rncbc@rncbc.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues)
Date: Wed, 15 Mar 2006 11:19:32 +0100	[thread overview]
Message-ID: <4417EA34.20802@tglx.de> (raw)
In-Reply-To: <20060315093122.GA1682@elte.hu>

Hi,

> a better fix would be the one below - it still does the call on the 
> current CPU, and skips other CPUs (on SMP). Does this solve the problem 
> on your box too?

Tested in all a hurry and it seems to work for me too.

Cheers,
JAN

  reply	other threads:[~2006-03-15 10:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 12:11 realtime-preempt patch-2.6.15-rt18 issues Rui Nuno Capela
2006-03-06 12:35 ` Ingo Molnar
2006-03-06 13:24 ` Ingo Molnar
2006-03-06 15:10   ` Rui Nuno Capela
2006-03-07  9:40     ` [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues) Jan Altenberg
2006-03-07 11:27       ` Ingo Molnar
2006-03-07 12:33       ` Rui Nuno Capela
2006-03-10  7:44         ` realtime-preempt patch-2.6.15-rt18 issues Jan Altenberg
2006-03-14 23:13         ` [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues) karsten wiese
2006-03-15  9:31           ` Ingo Molnar
2006-03-15 10:19             ` Jan Altenberg [this message]
2006-03-15 11:04               ` Ingo Molnar
2006-03-15 14:08                 ` karsten wiese
  -- strict thread matches above, loose matches on Subject: below --
2006-03-08 17:15 Rui Nuno Capela

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=4417EA34.20802@tglx.de \
    --to=tb10alj@tglx.de \
    --cc=annabellesgarden@yahoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rncbc@rncbc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox