From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Michael Neuling <mikey@neuling.org>, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [1/2] KVM: PPC: Book3S HV: Fix ppc_breakpoint_available compile error
Date: Wed, 4 Apr 2018 02:03:44 +1000 (AEST) [thread overview]
Message-ID: <40Fv5r73CLz9s21@ozlabs.org> (raw)
In-Reply-To: <20180401055036.18078-2-npiggin@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Sun, 2018-04-01 at 05:50:35 UTC, Nicholas Piggin wrote:
> arch/powerpc/kvm/book3s_hv.c: In function ‘kvmppc_h_set_mode’:
> arch/powerpc/kvm/book3s_hv.c:745:8: error: implicit declaration of function ‘ppc_breakpoint_available’; did you mean ‘hw_breakpoint_disable’? [-Werror=implicit-function-declaration]
> if (!ppc_breakpoint_available())
> ^~~~~~~~~~~~~~~~~~~~~~~~
> hw_breakpoint_disable
>
> Cc: Michael Neuling <mikey@neuling.org>
> Fixes: 398e712c00 ("KVM: PPC: Book3S HV: Return error from h_set_mode(SET_DAWR) on POWER9")
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/e303c08787c4cbe1ca07912817dff2
cheers
next prev parent reply other threads:[~2018-04-03 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 5:50 [PATCH 0/2] couple of minor DAWR fixes Nicholas Piggin
2018-04-01 5:50 ` [PATCH 1/2] KVM: PPC: Book3S HV: Fix ppc_breakpoint_available compile error Nicholas Piggin
2018-04-03 16:03 ` Michael Ellerman [this message]
2018-04-01 5:50 ` [PATCH 2/2] powerpc: Fix DABR write in the case of DAWR disabled Nicholas Piggin
2018-04-01 7:40 ` Nicholas Piggin
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=40Fv5r73CLz9s21@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.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).