From: Robert Richter <robert.richter@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/1] oprofile: Convert oprofilefs_lock to raw_spinlock
Date: Thu, 4 Mar 2010 17:22:42 +0100 [thread overview]
Message-ID: <20100304162242.GP13205@erda.amd.com> (raw)
In-Reply-To: <20100217144121.650660618@linutronix.de>
On 17.02.10 14:41:59, Thomas Gleixner wrote:
> oprofilefs_lock needs to be a real spinlock on preempt-rt. Convert it
> to a raw_spinlock. No change for !RT kernels.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Robert Richter <robert.richter@amd.com>
> ---
> arch/arm/oprofile/common.c | 4 ++--
> arch/x86/oprofile/nmi_int.c | 4 ++--
> drivers/oprofile/event_buffer.c | 4 ++--
> drivers/oprofile/oprofilefs.c | 6 +++---
> include/linux/oprofile.h | 2 +-
> 5 files changed, 10 insertions(+), 10 deletions(-)
Acked-by: Robert Richter <robert.richter@amd.com>
Thomas, do you want to send it upstream via RT updates?
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
prev parent reply other threads:[~2010-03-04 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 14:41 [patch 1/1] oprofile: Convert oprofilefs_lock to raw_spinlock Thomas Gleixner
2010-03-04 16:22 ` Robert Richter [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=20100304162242.GP13205@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-kernel@vger.kernel.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