From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.12.9-rt13
Date: Fri, 7 Feb 2014 11:41:07 +0100 [thread overview]
Message-ID: <20140207104107.GC23668@linutronix.de> (raw)
In-Reply-To: <20140205092657.GA21590@opentech.at>
* Nicholas Mc Guire | 2014-02-05 10:26:57 [+0100]:
>Sorry - this one causes a build failure with PREEMPT_RT_BASE=y and
>PREEMPT_RT_FULL not set.
At some point we are going to drop PREEMPT_RT_BASE because it was only
meant for debugging in the beginning. However I don't know when this
will be.
>The patch below fixes this build failure for 3.12.9-rt13.
>
>Not sure what the clean way of resolving this is - this patch proposes to
>move the spin_*_local into linux/locallock.h and map to spin_*lock for
>the "CONFIG_PREEMPT_RT_FULL not set" case.
>
>This was build tested with Preempt none,voluntary,low-lat,base,full and
>otherweise got only limited testing.
>
>I'm also not sure if putting the rt specific locks into locallock.h in
>this way is the proper way to deal with this #include dependency.
I think I keep it that way. However I split into two patches and add the
spin_lock_local => rt_spin_lock mapping in the rt-add-rt-locks.patch
where the locks are introduced.
Sebastian
prev parent reply other threads:[~2014-02-07 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 19:48 [ANNOUNCE] 3.12.9-rt13 Sebastian Andrzej Siewior
2014-02-04 7:26 ` Matthias Klein
2014-02-04 8:29 ` Pavel Vasilyev
2014-02-07 12:54 ` Sebastian Andrzej Siewior
2014-02-04 15:03 ` Mike Galbraith
2014-02-07 8:57 ` Sebastian Andrzej Siewior
2014-02-07 14:46 ` Mike Galbraith
2014-02-05 9:26 ` Nicholas Mc Guire
2014-02-07 10:41 ` Sebastian Andrzej Siewior [this message]
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=20140207104107.GC23668@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=der.herr@hofr.at \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).