From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "lkp@intel.com" <lkp@intel.com>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"CARLOS.PALMINHA@synopsys.com" <CARLOS.PALMINHA@synopsys.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"airlied@linux.ie" <airlied@linux.ie>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH 1/5 v4] drm: Add support of ARC PGU display controller
Date: Thu, 24 Mar 2016 21:12:12 +0000 [thread overview]
Message-ID: <1458853932.3068.13.camel@synopsys.com> (raw)
In-Reply-To: <201603250131.aMZWaAoR%fengguang.wu@intel.com>
Hello,
On Fri, 2016-03-25 at 01:37 +0800, kbuild test robot wrote:
> Hi Carlos,
>
> [auto build test ERROR on drm/drm-next]
> [also build test ERROR on v4.5 next-20160324]
> [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/20160325
> -005345
> base: git://people.freedesktop.org/~airlied/linux.git drm-next
> config: i386-allmodconfig (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
> 230 goto err_unload;
> 231
> > 232 ret = drm_connector_register_all(drm);
...
> > 254 drm_connector_unregister_all(drm);
> 255 drm_dev_unregister(drm);
That problem happens because that change relies on another series that yet
to be accepted in DRM for 4.7 cycle, see https://lkml.org/lkml/2016/3/23/128
Based on Daniel's comment I would assume soon after 4.6-rc1 will be cut
pending prerequisite will be applied to drm-next and that build failure will
go away.
-Alexey
next prev parent reply other threads:[~2016-03-24 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 16:48 [PATCH 0/5 v4] drm: Add support of ARC PGU display controller Alexey Brodkin
2016-03-24 16:48 ` [PATCH 1/5 " Alexey Brodkin
2016-03-24 17:37 ` kbuild test robot
2016-03-24 21:12 ` Alexey Brodkin [this message]
2016-03-24 16:48 ` [PATCH 2/5 v4] drm: Add DT bindings documentation for " Alexey Brodkin
2016-03-25 14:39 ` Rob Herring
2016-03-24 16:48 ` [PATCH 3/5 v4] MAINTAINERS: Add maintainer " Alexey Brodkin
2016-03-24 16:48 ` [PATCH 4/5 v4] arc: Add our own implementation of fb_pgprotect() Alexey Brodkin
2016-03-24 16:48 ` [PATCH 5/5 v4] 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=1458853932.3068.13.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=lkp@intel.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