linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: kbuild test robot <lkp@intel.com>,
	Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [kbuild-all] Error: Invalid compression type
Date: Wed, 1 Apr 2020 16:08:28 +0800	[thread overview]
Message-ID: <587d127c-1fc9-df46-033b-51eb7547b2b6@intel.com> (raw)
In-Reply-To: <202004011110.pULPETYO%lkp@intel.com>



On 4/1/20 11:28 AM, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   b3aa112d57b704441143d84b0475fb633a750035
> commit: 493a55f1e7724dee5e71bc726d5b819292094587 powerpc/xmon: Fix compile error in print_insn* functions
> date:   10 weeks ago
> config: powerpc-randconfig-a001-20200401 (attached as .config)
> compiler: powerpc-linux-gcc (GCC) 9.3.0
> reproduce:
>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>          chmod +x ~/bin/make.cross
>          git checkout 493a55f1e7724dee5e71bc726d5b819292094587
>          # save the attached .config to linux build tree
>          GCC_VERSION=9.3.0 make.cross ARCH=powerpc
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> Error: Invalid compression type

Please ignore this report, the error is from mkimage: 
https://github.com/u-boot/u-boot/blob/master/tools/mkimage.c#L178

Best Regards,
Rong Chen

>     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|-f auto|-F] [-b <dtb> [-b <dtb>]] [-i <ramdisk.cpio.gz>] fit-image
>     <dtb> file is used with -f auto, it may occur multiple times.
>     -D => set all options for device tree compiler
>     -f => input filename for FIT source
>     -i => input filename for ramdisk file
>     Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined)
>     /usr/bin/mkimage -V ==> print version information and exit
>     Use '-T list' to see a list of available image types
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org


      reply	other threads:[~2020-04-01  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01  3:28 Error: Invalid compression type kbuild test robot
2020-04-01  8:08 ` Rong Chen [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=587d127c-1fc9-df46-033b-51eb7547b2b6@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mpe@ellerman.id.au \
    --cc=sukadev@linux.vnet.ibm.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).