mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: dhowells@redhat.com, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-am33-list@redhat.com,
	kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [PATCH] mn10300: fix build error of missing fpu_save()
Date: Mon, 23 Jan 2017 23:26:18 +0000	[thread overview]
Message-ID: <7502.1485213978@warthog.procyon.org.uk> (raw)
In-Reply-To: <dc421c4f-4842-4429-1b99-92865c2f24b6@infradead.org>

Randy Dunlap <rdunlap@infradead.org> wrote:

> b. make <asm/switch_to.h> know about CONFIG_FPU not enabled
> 
> David, which one do you prefer?

b.

> From: Randy Dunlap <rdunlap@infradead.org>
> 
> When CONFIG_FPU is not enabled on arch/mn10300, <asm/switch_to.h>
> causes a build error with a call to fpu_save():
> 
> kernel/built-in.o: In function `.L410':
> core.c:(.sched.text+0x28a): undefined reference to `fpu_save'
> 
> Fix this by defining switch_fpu() in <asm/switch_to.h> only when
> CONFIG_FPU is enabled.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Cc:	David Howells <dhowells@redhat.com>
> ---
>  arch/mn10300/include/asm/switch_to.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- lnx-410-rc4.orig/arch/mn10300/include/asm/switch_to.h
> +++ lnx-410-rc4/arch/mn10300/include/asm/switch_to.h
> @@ -16,7 +16,7 @@
>  struct task_struct;
>  struct thread_struct;
>  
> -#if !defined(CONFIG_LAZY_SAVE_FPU)
> +#if defined(CONFIG_FPU) && !defined(CONFIG_LAZY_SAVE_FPU)
>  struct fpu_state_struct;
>  extern asmlinkage void fpu_save(struct fpu_state_struct *);
>  #define switch_fpu(prev, next)						\

Reviewed-by: David Howells <dhowells@redhat.com>

      reply	other threads:[~2017-01-23 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20  0:58 Randy Dunlap
2017-01-23 23:26 ` David Howells [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=7502.1485213978@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-am33-list@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@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 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®