linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, kbuild test robot <fengguang.wu@intel.com>,
	Josh Triplett <josh@joshtriplett.org>,
	linux-kernel@vger.kernel.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: mn10300, c6x: CONFIG_GENERIC_BUG must depend on CONFIG_BUG
Date: Mon, 29 Feb 2016 22:38:07 -0800	[thread overview]
Message-ID: <20160229223807.7d4723a0.akpm@linux-foundation.org> (raw)
In-Reply-To: <201603011418.lCbS3v2i%fengguang.wu@intel.com>

On Tue, 1 Mar 2016 14:18:56 +0800 kbuild test robot <lkp@intel.com> wrote:

> [auto build test ERROR on v4.5-rc6]
> [also build test ERROR on next-20160229]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
> 
> url:    https://github.com/0day-ci/linux/commits/Andrew-Morton/mn10300-c6x-CONFIG_GENERIC_BUG-must-depend-on-CONFIG_BUG/20160301-045134
> config: mn10300-allnoconfig (attached as .config)
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=mn10300 
> 
> All errors (new ones prefixed by >>):
> 
> >> arch/mn10300/kernel/fpu-nofpu.c:27:36: error: unknown type name 'elf_fpregset_t'
>     int dump_fpu(struct pt_regs *regs, elf_fpregset_t *fpreg)

hm, that error isn't well correlated with that patch!

This, I suppose.  I don't have an mn10300 cross-compiler.



From: Andrew Morton <akpm@linux-foundation.org>
Subject: arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h

 arch/mn10300/kernel/fpu-nofpu.c:27:36: error: unknown type name 'elf_fpregset_t'
    int dump_fpu(struct pt_regs *regs, elf_fpregset_t *fpreg)

Reported-by: kbuild test robot <lkp@intel.com>
Cc: Josh Triplett <josh@joshtriplett.org>
Cc: David Howells <dhowells@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 arch/mn10300/kernel/fpu-nofpu.c |    1 +
 1 file changed, 1 insertion(+)

diff -puN arch/mn10300/kernel/fpu-nofpu.c~a arch/mn10300/kernel/fpu-nofpu.c
--- a/arch/mn10300/kernel/fpu-nofpu.c~a
+++ a/arch/mn10300/kernel/fpu-nofpu.c
@@ -9,6 +9,7 @@
  * 2 of the Licence, or (at your option) any later version.
  */
 #include <asm/fpu.h>
+#include <asm/elf.h>
 
 /*
  * handle an FPU operational exception
_

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2016-03-01  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 23:33 include/linux/bug.h:93:12: error: dereferencing pointer to incomplete type kbuild test robot
2016-02-29 20:49 ` Andrew Morton
2016-02-29 21:24   ` Josh Triplett
2016-03-01  6:18   ` mn10300, c6x: CONFIG_GENERIC_BUG must depend on CONFIG_BUG kbuild test robot
2016-03-01  6:38     ` Andrew Morton [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=20160229223807.7d4723a0.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=josh@joshtriplett.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    /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).