From: Fengguang Wu <fengguang.wu@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
Date: Tue, 1 Mar 2016 10:26:52 +0800 [thread overview]
Message-ID: <20160301022652.GA20536@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1602281022410.3638@nanos>
On Sun, Feb 28, 2016 at 10:24:42AM +0100, Thomas Gleixner wrote:
> On Sun, 28 Feb 2016, kbuild test robot wrote:
>
> > Hi Thomas,
> >
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 691429e13dfaf5b0994b07cc166db41bd608ee3d
> > commit: dcaab54e348c5b66cca4802815ceebd37059e70c timekeeping: Remove ktime_get_monotonic_offset()
> > date: 1 year, 7 months ago
> > config: xtensa-common_defconfig (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
> > git checkout dcaab54e348c5b66cca4802815ceebd37059e70c
> > # save the attached .config to linux build tree
> > make.cross ARCH=xtensa
> >
> > All errors (new ones prefixed by >>):
> >
> > >> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
> > Usage: /usr/bin/mkimage -l image
> > -l ==> list image header information
> > /usr/bin/mkimage -A arch -O os -T type -C comp -a addr -e ep -n name -d image
> > -A ==> set architecture to 'arch'
> > -O ==> set operating system to 'os'
> > -T ==> set image type to 'type'
> > -C ==> set compression type 'comp'
> > -a ==> set load address to 'addr' (hex)
> > ==> set entry point to 'ep' (hex)
> > ==> set image name to 'name'-d ==> use image data from 'datafile'
> > -x ==> set XIP (execute in place)
> > /usr/bin/mkimage [-D dtc_options] -f fit-image.its fit-image
> > /usr/bin/mkimage -V ==> print version information and exit
>
> How is removing a unused function related to a tool problem?
Sorry, I triggered a batch of bisects for aged errors. This one looks
a problem with the tool rather than regression by some kernel commit.
Which confused the bisect.
> Hint:
>
> >> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips,\
> mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
>
> Your mkimage does not support xtensa .....
Yeah, just upgraded the mkimage tool!
Thanks,
Fengguang
prev parent reply other threads:[~2016-03-01 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 23:51 kbuild test robot
2016-02-28 8:43 ` Geert Uytterhoeven
2016-03-01 2:06 ` [kbuild-all] " Fengguang Wu
2016-03-01 2:48 ` Fengguang Wu
2016-03-01 3:15 ` Michael Ellerman
2016-03-01 3:30 ` Fengguang Wu
2016-02-28 9:24 ` Thomas Gleixner
2016-03-01 2:26 ` Fengguang Wu [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=20160301022652.GA20536@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=john.stultz@linaro.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®