From: Paul Mackerras <paulus@samba.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: warrier@linux.vnet.ibm.com, linuxppc-dev@ozlabs.org, agraf@suse.de
Subject: Re: [PATCH] powerpc/kvm: Fix SMP=n build error in book3s_xics.c
Date: Tue, 28 Apr 2015 14:36:12 +1000 [thread overview]
Message-ID: <20150428043612.GA28239@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <1430181767-2193-1-git-send-email-mpe@ellerman.id.au>
On Tue, Apr 28, 2015 at 10:42:47AM +1000, Michael Ellerman wrote:
> Commit 34cb7954c0aa "Convert ICS mutex lock to spin lock" added an
> include of asm/spinlock.h, which does not work in the SMP=n case.
>
> It should instead include linux/spinlock.h
>
> Fixes: 34cb7954c0aa ("KVM: PPC: Book3S HV: Convert ICS mutex lock to spin lock")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Acked-by: Paul Mackerras <paulus@samba.org>
next prev parent reply other threads:[~2015-04-28 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 0:42 [PATCH] powerpc/kvm: Fix SMP=n build error in book3s_xics.c Michael Ellerman
2015-04-28 4:36 ` Paul Mackerras [this message]
2015-04-28 7:51 ` Alexander Graf
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=20150428043612.GA28239@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=warrier@linux.vnet.ibm.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).