From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: balbi@ti.com, Thomas Gleixner <tglx@linutronix.de>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: omap: make wakeupgen_lock raw
Date: Fri, 1 Feb 2013 14:38:36 -0800 [thread overview]
Message-ID: <20130201223836.GC22517@atomide.com> (raw)
In-Reply-To: <51023995.1050703@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [130124 23:54]:
> On Thursday 24 January 2013 11:52 PM, Felipe Balbi wrote:
> >Hi,
> >
> >On Fri, Dec 07, 2012 at 04:49:47PM +0200, Felipe Balbi wrote:
> >>From: Thomas Gleixner <tglx@linutronix.de>
> >>
> >>When applying RT patch on top of Linux, spinlocks are
> >>implemented as RT-mutexes, which means they are preemptable.
> >>
> >>Current GIC implementation on OMAP is using a spinlock
> >>to protect against preemption. As it turns out, we need
> >>to convert that lock into a raw_spinlock so that OMAP's
> >>interrupt controller works as expected after RT-patch
> >>is applied.
> >>
> >>This patch is simply to decrease the amount of changes
> >>RT-team needs to carry out of tree. It doesn't cause any
> >>changes in behavior.
> >>
> >>Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> >>Signed-off-by: Felipe Balbi <balbi@ti.com>
> >
> Sorry i missed this patch. Tony can you please
> pick it up?
>
> For the patch,
> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
Looks like no comments, so applying this into
omap-for-v3.9/fixes-non-critical.
Regards,
Tony
prev parent reply other threads:[~2013-02-01 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 14:49 [PATCH] arm: omap: make wakeupgen_lock raw Felipe Balbi
2013-01-24 18:22 ` Felipe Balbi
2013-01-25 7:51 ` Santosh Shilimkar
2013-02-01 22:38 ` Tony Lindgren [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=20130201223836.GC22517@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--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).