mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: Paul Burton <paulburton@kernel.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: asm: fix warning when disabling MIPS_FP_SUPPORT
Date: Wed, 30 Oct 2024 12:16:09 +0100	[thread overview]
Message-ID: <ZyIVeSZpqG1co4z6@alpha.franken.de> (raw)
In-Reply-To: <20241012-mips-fcr31-warning-v1-1-bac1d869d775@gmail.com>

On Sat, Oct 12, 2024 at 12:12:14PM +0200, Jonas Gorski wrote:
> When MIPS_FP_SUPPORT is disabled, __sanitize_fcr31() is defined as
> nothing, which triggers a gcc warning:
> 
>     In file included from kernel/sched/core.c:79:
>     kernel/sched/core.c: In function 'context_switch':
>     ./arch/mips/include/asm/switch_to.h:114:39: warning: suggest braces around empty body in an 'if' statement [-Wempty-body]
>       114 |                 __sanitize_fcr31(next);                                 \
>           |                                       ^
>     kernel/sched/core.c:5316:9: note: in expansion of macro 'switch_to'
>      5316 |         switch_to(prev, next, prev);
>           |         ^~~~~~~~~
> 
> Fix this by providing an empty body for __sanitize_fcr31() like one is
> defined for __mips_mt_fpaff_switch_to().
> 
> Fixes: 36a498035bd2 ("MIPS: Avoid FCSR sanitization when CONFIG_MIPS_FP_SUPPORT=n")
> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
> ---
>  arch/mips/include/asm/switch_to.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mips/include/asm/switch_to.h b/arch/mips/include/asm/switch_to.h
> index a4374b4cb88fd830f8b83caab52d6e3c133fd0c4..d6ccd53440213315ec75a54caf683c32c69dcdbe 100644
> --- a/arch/mips/include/asm/switch_to.h
> +++ b/arch/mips/include/asm/switch_to.h
> @@ -97,7 +97,7 @@ do {									\
>  	}								\
>  } while (0)
>  #else
> -# define __sanitize_fcr31(next)
> +# define __sanitize_fcr31(next) do { (void) (next); } while (0)
>  #endif
>  
>  /*
> 
> ---
> base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
> change-id: 20241012-mips-fcr31-warning-d4eebcfc91c5

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2024-10-30 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-12 10:12 Jonas Gorski
2024-10-12 13:09 ` Maciej W. Rozycki
2024-10-30 11:16 ` Thomas Bogendoerfer [this message]

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=ZyIVeSZpqG1co4z6@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@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

all inboxes | Powered by JetHome®