From: Frank Rowand <frank.rowand@am.sony.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Rowand, Frank" <Frank_Rowand@sonyusa.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [ANNOUNCE] 3.0-rt4
Date: Wed, 27 Jul 2011 15:27:47 -0700 [thread overview]
Message-ID: <4E3090E3.7000100@am.sony.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1107280004410.2660@ionos>
On 07/27/11 15:05, Thomas Gleixner wrote:
> On Wed, 27 Jul 2011, Frank Rowand wrote:
>
>> On 07/27/11 14:37, Thomas Gleixner wrote:
>>> Dear RT Folks,
>>>
>>> I'm pleased to announce the 3.0-rt4 release.
>>
>> ARM panda board, PREEMPT_RT_FULL
>>
>> -rt3 compiled OK. -rt4 compile fails:
>>
>>
>> mm/init-mm.c:24: error: unknown field 'lock' specified in initializer
>> mm/init-mm.c:24: error: unknown field 'wait_lock' specified in initializer
>> mm/init-mm.c:24: error: incompatible types in initialization
>> mm/init-mm.c:24: error: unknown field 'save_state' specified in initializer
>> mm/init-mm.c:24: warning: excess elements in struct initializer
>> mm/init-mm.c:24: warning: (near initialization for 'init_mm.context.id_lock.raw_lock')
>
> Bah, that's what I get for trying to vanish. Fix below.
>
> --- linux-2.6.orig/arch/arm/include/asm/mmu.h
> +++ linux-2.6/arch/arm/include/asm/mmu.h
> @@ -16,7 +16,7 @@ typedef struct {
>
> /* init_mm.context.id_lock should be initialized. */
> #define INIT_MM_CONTEXT(name) \
> - .context.id_lock = __SPIN_LOCK_UNLOCKED(name.context.id_lock),
> + .context.id_lock = __RAW_SPIN_LOCK_UNLOCKED(name.context.id_lock),
> #else
> #define ASID(mm) (0)
> #endif
Thanks!
Compiles and boots.
-Frank
next prev parent reply other threads:[~2011-07-27 22:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 21:37 [ANNOUNCE] 3.0-rt4 Thomas Gleixner
2011-07-27 21:57 ` Frank Rowand
2011-07-27 22:05 ` Thomas Gleixner
2011-07-27 22:27 ` Frank Rowand [this message]
2011-07-28 7:33 ` Nikita V. Youshchenko
2011-07-28 8:06 ` Thomas Gleixner
2011-07-28 8:24 ` Nikita V. Youshchenko
2011-07-28 8:44 ` Peter Zijlstra
2011-07-28 8:51 ` Nikita V. Youshchenko
2011-07-28 9:21 ` Anca Emanuel
2011-07-28 16:10 ` Thomas Gleixner
2011-07-28 9:37 ` Thomas Gleixner
2011-07-28 8:43 ` Peter Zijlstra
2011-07-28 9:41 ` Yong Zhang
2011-07-28 9:49 ` Thomas Gleixner
2011-07-28 11:22 ` N, Mugunthan V
2011-07-28 11:36 ` Thomas Gleixner
2011-07-28 15:59 ` hermann
2011-07-28 17:41 ` Paul E. McKenney
2011-07-28 17:43 ` Thomas Gleixner
2011-07-28 18:32 ` Paul E. McKenney
2011-07-28 19:05 ` Thomas Gleixner
2011-07-28 19:34 ` Paul E. McKenney
2011-07-28 20:29 ` Paul E. McKenney
2011-07-28 17:42 ` Jason Wessel
2011-07-28 17:49 ` Thomas Gleixner
2011-07-28 19:16 ` Fernando Lopez-Lezcano
2011-07-28 19:36 ` Thomas Gleixner
2011-07-29 0:13 ` Fernando Lopez-Lezcano
2011-07-28 21:22 ` Peter Zijlstra
2011-07-28 22:55 ` Pekka Enberg
2011-07-29 0:17 ` Fernando Lopez-Lezcano
2011-08-04 8:36 ` [tip:core/urgent] slab, lockdep: Annotate the locks before using them tip-bot for Peter Zijlstra
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=4E3090E3.7000100@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=Frank_Rowand@sonyusa.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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