linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-fbdev@vger.kernel.org, kbuild-all@01.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] video: fbdev: gbefb: add COMPILE_TEST support
Date: Sat, 13 Apr 2019 19:42:11 +0000	[thread overview]
Message-ID: <201904140340.VBtIMA2i%lkp@intel.com> (raw)
In-Reply-To: <daeed9ce-710b-cf70-88b5-8a493a082211@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

Hi Bartlomiej,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc4 next-20190412]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Bartlomiej-Zolnierkiewicz/video-fbdev-gbefb-add-COMPILE_TEST-support/20190413-072821
config: arm-allyesconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.2.0 make.cross ARCH=arm 

All errors (new ones prefixed by >>):

   drivers/video/fbdev/gbefb.o: In function `gbe_turn_off':
>> gbefb.c:(.text+0x9b8): undefined reference to `__bad_udelay'
   gbefb.c:(.text+0xa0c): undefined reference to `__bad_udelay'
   drivers/video/fbdev/gbefb.o: In function `gbe_turn_on':
   gbefb.c:(.text+0xb64): undefined reference to `__bad_udelay'
   gbefb.c:(.text+0xbb0): undefined reference to `__bad_udelay'
   drivers/video/fbdev/gbefb.o: In function `gbefb_set_par':
   gbefb.c:(.text+0xda4): undefined reference to `__bad_udelay'

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67480 bytes --]

      reply	other threads:[~2019-04-13 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190412115351eucas1p1dc215edd8d8c3d2dda99663925939290@eucas1p1.samsung.com>
2019-04-12 11:53 ` [PATCH] video: fbdev: gbefb: add COMPILE_TEST support Bartlomiej Zolnierkiewicz
2019-04-13 19:42   ` kbuild test robot [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=201904140340.VBtIMA2i%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).