public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, dwalker@mvista.com,
	Joe King <atom_bomb@rocketmail.com>,
	ganzinger@mvista.com, Lee Revell <rlrevell@joe-job.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.12-rc4-V0.7.47-06
Date: Mon, 30 May 2005 18:47:41 +0200	[thread overview]
Message-ID: <429B43AD.5060003@stud.feec.vutbr.cz> (raw)
In-Reply-To: <20050530145016.GA18433@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
>>agreed - i've added your patch to my tree.
> 
> with a small modification: i turned the error into a link-time error, 
> because gcc parses both branches and will give a compiler-time warning 
> even if the proper compat_semaphore is used.

Oh, sorry. I actually had it produce a link-time error at first. But I 
wanted so much to make it fail at compile time that I screwed it up and 
didn't test both cases.

However, what you have in RT-V0.7.47-13 is still not correct. Now it 
again produces only a warning :-)
Patch attached. This time I really tested it in both cases. For struct 
semaphore it fails at link-time. For struct compat_semaphore it compiles 
without problems.

Michal

[-- Attachment #2: rt_init_MUTEX_LOCKED.diff --]
[-- Type: text/x-patch, Size: 707 bytes --]

diff -Nurp -X linux-RT/Documentation/dontdiff linux-RT/include/linux/rt_lock.h linux-RT.mich/include/linux/rt_lock.h
--- linux-RT/include/linux/rt_lock.h	2005-05-30 18:40:07.000000000 +0200
+++ linux-RT.mich/include/linux/rt_lock.h	2005-05-30 18:29:53.000000000 +0200
@@ -210,7 +210,7 @@ extern void there_is_no_init_MUTEX_LOCKE
  * No locked initialization for RT semaphores
  */
 #define rt_init_MUTEX_LOCKED(sem) \
-		there_is_no_init_MUTEX_LOCKED_for_RT_semaphores
+		there_is_no_init_MUTEX_LOCKED_for_RT_semaphores()
 extern void FASTCALL(rt_down(struct semaphore *sem));
 extern int FASTCALL(rt_down_interruptible(struct semaphore *sem));
 extern int FASTCALL(rt_down_trylock(struct semaphore *sem));

  reply	other threads:[~2005-05-30 16:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23  8:26 [patch] Real-Time Preemption, -RT-2.6.12-rc4-V0.7.47-06 Ingo Molnar
2005-05-23  9:34 ` Serge Noiraud
2005-05-23 11:23   ` Ingo Molnar
2005-05-23 14:30     ` K.R. Foley
2005-05-24 16:38 ` K.R. Foley
2005-05-25 11:34   ` Ingo Molnar
2005-05-25 11:35     ` Ingo Molnar
2005-05-25 13:28       ` K.R. Foley
2005-05-25 14:03         ` Ingo Molnar
2005-05-25 14:18           ` K.R. Foley
2005-05-25 15:20           ` K.R. Foley
2005-05-26  7:45           ` Ingo Molnar
2005-05-26 10:53             ` K.R. Foley
2005-05-26 15:23             ` K.R. Foley
2005-05-25 20:38 ` Michal Schmidt
2005-05-27 20:46   ` Michal Schmidt
2005-05-28  5:53     ` Ingo Molnar
2005-05-30  9:51       ` Michal Schmidt
2005-05-30 14:38         ` Ingo Molnar
2005-05-30 14:50           ` Ingo Molnar
2005-05-30 16:47             ` Michal Schmidt [this message]
2005-05-30 18:09               ` Ingo Molnar
2005-06-01 17:28       ` Esben Nielsen
2005-06-01  9:19   ` Ingo Molnar
2005-06-01  9:32     ` Michal Schmidt
2005-06-01  9:39       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2005-05-23 15:05 Oleg Nesterov
2005-05-23 15:12 ` Daniel Walker
2005-05-23 15:53   ` Oleg Nesterov
2005-05-23 16:48   ` Oleg Nesterov
2005-06-01  9:21     ` Ingo Molnar
2005-06-01 13:04       ` Daniel Walker
2005-06-01 13:11         ` Ingo Molnar
2005-06-01 13:21           ` Daniel Walker
2005-06-01 14:43         ` Oleg Nesterov
2005-06-01 14:43           ` Daniel Walker
2005-06-01 15:02             ` Oleg Nesterov
2005-06-01 15:05               ` Daniel Walker
2005-06-01 15:47                 ` Oleg Nesterov
2005-06-01 15:43                   ` Daniel Walker
2005-05-24  1:47 Perez-Gonzalez, Inaky

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=429B43AD.5060003@stud.feec.vutbr.cz \
    --to=xschmi00@stud.feec.vutbr.cz \
    --cc=atom_bomb@rocketmail.com \
    --cc=dwalker@mvista.com \
    --cc=ganzinger@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.com \
    --cc=rostedt@goodmis.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