From: Avi Kivity <avi@redhat.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"avi@qumranet.com" <avi@qumranet.com>
Subject: Re: next-20081107: ia64 vs kvm
Date: Sun, 09 Nov 2008 12:00:14 +0200 [thread overview]
Message-ID: <4916B4AE.50101@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC21983F9EB@pdsmsx503.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> Alexey Dobriyan wrote:
>
>> On ia64-smp-n-debug-n-preempt-n:
>>
>> arch/ia64/kvm/vmm.c:63: error: 'raw_spinlock_t' has no member named
>> 'lock'
>>
>>
> Hi, Avi
> This patch should fix the issue Alex met, please apply to kvm.git and queue it for 2.6.28 fixes. Thanks!
> Xiantao
>
> From fae5782b369f4bd6e8edecad5912fea7624f0374 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Sat, 8 Nov 2008 15:46:59 +0800
> Subject: [PATCH] KVM: IA64: Fix vmm_spin_{un}lock for !CONFIG_SMP.
>
> In the case of !CONFIG_SMP, raw_spinlock_t has no any member
> so vmm_spin_lock should also defines the version for !CONFIG_SMP.
>
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-09 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 9:54 linux-next: Tree for November 7 Stephen Rothwell
2008-11-07 22:30 ` next-20081107: ia64 vs kvm Alexey Dobriyan
2008-11-08 7:57 ` Zhang, Xiantao
2008-11-09 10:00 ` Avi Kivity [this message]
2008-11-07 23:04 ` linux-next: Tree for November 7 Alexey Dobriyan
2008-11-08 11:57 ` Bartlomiej Zolnierkiewicz
2008-11-08 18:43 ` Alexey Dobriyan
2008-11-08 19:13 ` Bartlomiej Zolnierkiewicz
2008-11-10 6:45 ` KAMEZAWA Hiroyuki
2008-11-10 8:12 ` KAMEZAWA Hiroyuki
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=4916B4AE.50101@redhat.com \
--to=avi@redhat.com \
--cc=adobriyan@gmail.com \
--cc=avi@qumranet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xiantao.zhang@intel.com \
/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).