All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: kbuild-all@01.org, linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: [linuxtv-media:request_api 77/78] cedrus_hw.c:undefined reference to `sunxi_sram_release'
Date: Sat, 13 Oct 2018 03:28:10 +0800	[thread overview]
Message-ID: <201810130346.yrpGVoXI%fengguang.wu@intel.com> (raw)

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

tree:   git://linuxtv.org/media_tree.git request_api
head:   e4183d3256e3cd668e899d06af66da5aac3a51af
commit: 50e761516f2b8c0cdeb31a8c6ca1b4ef98cd13f1 [77/78] media: platform: Add Cedrus VPU decoder driver
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        git checkout 50e761516f2b8c0cdeb31a8c6ca1b4ef98cd13f1
        # save the attached .config to linux build tree
        make ARCH=i386 

Note: the linuxtv-media/request_api HEAD e4183d3256e3cd668e899d06af66da5aac3a51af builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   drivers/staging/media/sunxi/cedrus/cedrus_hw.o: In function `cedrus_hw_remove':
>> cedrus_hw.c:(.text+0x39a): undefined reference to `sunxi_sram_release'

---
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: 64491 bytes --]

                 reply	other threads:[~2018-10-13  3:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201810130346.yrpGVoXI%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kbuild-all@01.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=paul.kocialkowski@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.