mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: kbuild-all@01.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	Carlos Palminha <CARLOS.PALMINHA@synopsys.com>,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	David Airlie <airlied@linux.ie>,
	linux-snps-arc@lists.infradead.org
Subject: Re: [PATCH 1/5 v5] drm: Add support of ARC PGU display controller
Date: Sun, 3 Apr 2016 07:13:59 +0800	[thread overview]
Message-ID: <201604030718.oT12hIrh%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459164999-11850-2-git-send-email-abrodkin@synopsys.com>

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

Hi Carlos,

[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.6-rc1 next-20160401]
[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/Alexey-Brodkin/drm-Add-support-of-ARC-PGU-display-controller/20160328-194009
base:   git://people.freedesktop.org/~airlied/linux.git drm-next
config: x86_64-allmodconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/gpu/drm/arc/arcpgu_drv.c: In function 'arcpgu_probe':
>> drivers/gpu/drm/arc/arcpgu_drv.c:232:8: error: implicit declaration of function 'drm_connector_register_all' [-Werror=implicit-function-declaration]
     ret = drm_connector_register_all(drm);
           ^
   drivers/gpu/drm/arc/arcpgu_drv.c: In function 'arcpgu_remove':
   drivers/gpu/drm/arc/arcpgu_drv.c:254:2: error: implicit declaration of function 'drm_connector_unregister_all' [-Werror=implicit-function-declaration]
     drm_connector_unregister_all(drm);
     ^
   cc1: some warnings being treated as errors

vim +/drm_connector_register_all +232 drivers/gpu/drm/arc/arcpgu_drv.c

   226			goto err_unref;
   227	
   228		ret = drm_dev_register(drm, 0);
   229		if (ret)
   230			goto err_unload;
   231	
 > 232		ret = drm_connector_register_all(drm);
   233		if (ret)
   234			goto err_unregister;
   235	

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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 53176 bytes --]

  reply	other threads:[~2016-04-02 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 11:36 [PATCH 0/5 " Alexey Brodkin
2016-03-28 11:36 ` [PATCH 1/5 " Alexey Brodkin
2016-04-02 23:13   ` kbuild test robot [this message]
2016-03-28 11:36 ` [PATCH 2/5 v5] drm: Add DT bindings documentation for " Alexey Brodkin
2016-03-28 11:36 ` [PATCH 3/5 v5] MAINTAINERS: Add maintainer " Alexey Brodkin
2016-03-28 11:36 ` [PATCH 4/5 v5] arc: Add our own implementation of fb_pgprotect() Alexey Brodkin
2016-04-05 18:35   ` Alexey Brodkin
2016-03-28 11:36 ` [PATCH 5/5 v5] arc: axs10x - add support of ARC PGU Alexey Brodkin

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=201604030718.oT12hIrh%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.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

all inboxes | Powered by JetHome®