From: Thomas Gleixner <tglx@linutronix.de>
To: Jan Blunck <jblunck@suse.de>
Cc: rt-users <linux-rt-users@vger.kernel.org>, kvm@vger.kernel.org
Subject: Re: [patch 2/3] kvm: convert spin-locks to raw_spinlock_t
Date: Thu, 9 Apr 2009 15:48:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0904091547540.21577@localhost.localdomain> (raw)
In-Reply-To: <20090407235902.400480759@suse.de>
On Wed, 8 Apr 2009, Jan Blunck wrote:
> This patch converts some KVM spin-locks to be of type raw_spinlock_t.
Applied. Thanks,
tglx
next prev parent reply other threads:[~2009-04-09 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 23:58 [patch 0/3] Patches for KVM & RT Jan Blunck
2009-04-07 23:58 ` [patch 1/3] Make rt_down_read_trylock() behave like down_read_trylock() Jan Blunck
2009-04-09 13:47 ` Thomas Gleixner
2009-04-07 23:58 ` [patch 2/3] kvm: convert spin-locks to raw_spinlock_t Jan Blunck
2009-04-09 9:21 ` Marcelo Tosatti
2009-04-09 13:48 ` Thomas Gleixner [this message]
2009-04-07 23:58 ` [patch 3/3] kvm: wake up waitqueue before calling get_cpu() Jan Blunck
2009-04-09 9:24 ` Marcelo Tosatti
2009-04-09 13:48 ` Thomas Gleixner
2009-04-09 21:44 ` [patch 0/3] Patches for KVM & RT Carsten Emde
2009-04-10 7:23 ` Thomas Gleixner
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=alpine.LFD.2.00.0904091547540.21577@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=jblunck@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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