From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joel Stanley <joel@jms.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH] powerpc/security: Fix build break
Date: Wed, 15 May 2019 07:18:30 +0200 [thread overview]
Message-ID: <20190515051830.GA18166@kroah.com> (raw)
In-Reply-To: <20190515045206.10610-1-joel@jms.id.au>
On Wed, May 15, 2019 at 02:22:06PM +0930, Joel Stanley wrote:
> This fixes a build break introduced in with the recent round of CPU
> bug patches.
>
> arch/powerpc/kernel/security.c: In function ‘setup_barrier_nospec’:
> arch/powerpc/kernel/security.c:59:21: error: implicit declaration of
> function ‘cpu_mitigations_off’ [-Werror=implicit-function-declaration]
> if (!no_nospec && !cpu_mitigations_off())
> ^~~~~~~~~~~~~~~~~~~
>
> Fixes: 782e69efb3df ("powerpc/speculation: Support 'mitigations=' cmdline option")
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> This should be applied to the 4.14 and 4.19 trees. There is no issue
> with 5.1. The commit message contains a fixes line for the commit in
> Linus tree.
> ---
> arch/powerpc/kernel/security.c | 1 +
> 1 file changed, 1 insertion(+)
Isn't this just commit 42e2acde1237 ("powerpc/64s: Include cpu header")?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/security: Fix build break
Date: Wed, 15 May 2019 07:18:30 +0200 [thread overview]
Message-ID: <20190515051830.GA18166@kroah.com> (raw)
In-Reply-To: <20190515045206.10610-1-joel@jms.id.au>
On Wed, May 15, 2019 at 02:22:06PM +0930, Joel Stanley wrote:
> This fixes a build break introduced in with the recent round of CPU
> bug patches.
>
> arch/powerpc/kernel/security.c: In function ‘setup_barrier_nospec’:
> arch/powerpc/kernel/security.c:59:21: error: implicit declaration of
> function ‘cpu_mitigations_off’ [-Werror=implicit-function-declaration]
> if (!no_nospec && !cpu_mitigations_off())
> ^~~~~~~~~~~~~~~~~~~
>
> Fixes: 782e69efb3df ("powerpc/speculation: Support 'mitigations=' cmdline option")
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> This should be applied to the 4.14 and 4.19 trees. There is no issue
> with 5.1. The commit message contains a fixes line for the commit in
> Linus tree.
> ---
> arch/powerpc/kernel/security.c | 1 +
> 1 file changed, 1 insertion(+)
Isn't this just commit 42e2acde1237 ("powerpc/64s: Include cpu header")?
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-15 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 4:52 [PATCH] powerpc/security: Fix build break Joel Stanley
2019-05-15 4:52 ` Joel Stanley
2019-05-15 5:18 ` Greg Kroah-Hartman [this message]
2019-05-15 5:18 ` Greg Kroah-Hartman
2019-05-15 6:08 ` Greg Kroah-Hartman
2019-05-15 6:08 ` Greg Kroah-Hartman
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=20190515051830.GA18166@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.