linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390: Replace IS_ENABLED(EXPOLINE_*) with IS_ENABLED(CONFIG_EXPOLINE_*)
Date: Mon, 19 Feb 2018 06:29:09 +0000	[thread overview]
Message-ID: <20180219072909.4199211e@mschwideX1> (raw)
In-Reply-To: <20180217231029.32111-1-rosca.eugeniu@gmail.com>

On Sun, 18 Feb 2018 00:10:29 +0100
Eugeniu Rosca <roscaeugeniu@gmail.com> wrote:

> From: Eugeniu Rosca <erosca@de.adit-jv.com>
> 
> I've accidentally stumbled upon the IS_ENABLED(EXPOLINE_*) lines, which
> obviously always evaluate to false. Fix this.
> 
> Fixes: f19fbd5ed642 ("s390: introduce execute-trampolines for branches")
> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
> ---
>  arch/s390/kernel/nospec-branch.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/s390/kernel/nospec-branch.c b/arch/s390/kernel/nospec-branch.c
> index 69d7fcf48158..9aff72d3abda 100644
> --- a/arch/s390/kernel/nospec-branch.c
> +++ b/arch/s390/kernel/nospec-branch.c
> @@ -2,8 +2,8 @@
>  #include <linux/module.h>
>  #include <asm/nospec-branch.h>
> 
> -int nospec_call_disable = IS_ENABLED(EXPOLINE_OFF);
> -int nospec_return_disable = !IS_ENABLED(EXPOLINE_FULL);
> +int nospec_call_disable = IS_ENABLED(CONFIG_EXPOLINE_OFF);
> +int nospec_return_disable = !IS_ENABLED(CONFIG_EXPOLINE_FULL);
> 
>  static int __init nospectre_v2_setup_early(char *str)
>  {

Applied, thank you!

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

           reply	other threads:[~2018-02-19  6:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20180217231029.32111-1-rosca.eugeniu@gmail.com>]

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=20180219072909.4199211e@mschwideX1 \
    --to=schwidefsky@de.ibm.com \
    --cc=linux-s390@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;
as well as URLs for NNTP newsgroup(s).