All of lore.kernel.org
 help / color / mirror / Atom feed
From: julien.thierry@arm.com (Julien Thierry)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: clean up per-processor check_bugs method call
Date: Thu, 20 Sep 2018 10:06:40 +0100	[thread overview]
Message-ID: <d4b5a153-f20b-c9e9-2b35-c57c0c6b8d06@arm.com> (raw)
In-Reply-To: <E1g2Z6U-0003eX-1M@rmk-PC.armlinux.org.uk>

Hi Russell,

On 19/09/18 10:49, Russell King wrote:
> Call the per-processor type check_bugs() method in the same way as we
> do other per-processor functions - move the "processor." detail into
> proc-fns.h.
> 

Reviewed-by: Julien Thierry <julien.thierry@arm.com>

> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> ---
>   arch/arm/include/asm/proc-fns.h | 1 +
>   arch/arm/kernel/bugs.c          | 4 ++--
>   2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/include/asm/proc-fns.h b/arch/arm/include/asm/proc-fns.h
> index e25f4392e1b2..30c499146320 100644
> --- a/arch/arm/include/asm/proc-fns.h
> +++ b/arch/arm/include/asm/proc-fns.h
> @@ -99,6 +99,7 @@ extern void cpu_do_suspend(void *);
>   extern void cpu_do_resume(void *);
>   #else
>   #define cpu_proc_init			processor._proc_init
> +#define cpu_check_bugs			processor.check_bugs
>   #define cpu_proc_fin			processor._proc_fin
>   #define cpu_reset			processor.reset
>   #define cpu_do_idle			processor._do_idle
> diff --git a/arch/arm/kernel/bugs.c b/arch/arm/kernel/bugs.c
> index 7be511310191..d41d3598e5e5 100644
> --- a/arch/arm/kernel/bugs.c
> +++ b/arch/arm/kernel/bugs.c
> @@ -6,8 +6,8 @@
>   void check_other_bugs(void)
>   {
>   #ifdef MULTI_CPU
> -	if (processor.check_bugs)
> -		processor.check_bugs();
> +	if (cpu_check_bugs)
> +		cpu_check_bugs();
>   #endif
>   }
>   
> 

-- 
Julien Thierry

  reply	other threads:[~2018-09-20  9:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  9:48 [PATCH 0/5] Spectre big.Little updates Russell King - ARM Linux
2018-09-19  9:48 ` [PATCH 1/5] ARM: make lookup_processor_type() non-__init Russell King
2018-09-20  9:07   ` Julien Thierry
2018-09-19  9:48 ` [PATCH 2/5] ARM: split out processor lookup Russell King
2018-09-20  9:05   ` Julien Thierry
2018-09-19  9:49 ` [PATCH 3/5] ARM: clean up per-processor check_bugs method call Russell King
2018-09-20  9:06   ` Julien Thierry [this message]
2018-09-19  9:49 ` [PATCH 4/5] ARM: add PROC_VTABLE macro Russell King
2018-09-20  9:07   ` Julien Thierry
2018-09-19  9:49 ` [PATCH 5/5] ARM: spectre-v2: per-CPU vtables to work around big.Little systems Russell King
2018-09-20  9:04   ` Julien Thierry
2018-09-20  9:21     ` Russell King - ARM Linux
2018-09-20  9:28       ` Julien Thierry
2018-10-05  9:09   ` Marek Szyprowski
2018-10-05  9:09     ` Marek Szyprowski
2018-10-05  9:35     ` Krzysztof Kozlowski
2018-10-05  9:35       ` Krzysztof Kozlowski
2018-10-05  9:46     ` Russell King - ARM Linux
2018-10-05  9:46       ` Russell King - ARM Linux
2018-10-30 10:50       ` Russell King - ARM Linux
2018-10-30 10:50         ` Russell King - ARM Linux
2018-10-31 15:21         ` Marek Szyprowski
2018-10-31 15:21           ` Marek Szyprowski
2018-10-31 18:12           ` Russell King - ARM Linux
2018-10-31 18:12             ` Russell King - ARM Linux
2018-11-02 17:17         ` Kevin Hilman
2018-11-02 17:17           ` Kevin Hilman

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=d4b5a153-f20b-c9e9-2b35-c57c0c6b8d06@arm.com \
    --to=julien.thierry@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.