From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey.Brodkin@synopsys.com (Alexey Brodkin) Date: Thu, 24 Mar 2016 21:12:12 +0000 Subject: [PATCH 1/5 v4] drm: Add support of ARC PGU display controller In-Reply-To: <201603250131.aMZWaAoR%fengguang.wu@intel.com> References: <201603250131.aMZWaAoR%fengguang.wu@intel.com> List-ID: Message-ID: <1458853932.3068.13.camel@synopsys.com> To: linux-snps-arc@lists.infradead.org Hello, On Fri, 2016-03-25@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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey Brodkin Subject: Re: [PATCH 1/5 v4] drm: Add support of ARC PGU display controller Date: Thu, 24 Mar 2016 21:12:12 +0000 Message-ID: <1458853932.3068.13.camel@synopsys.com> References: <201603250131.aMZWaAoR%fengguang.wu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-7" Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <201603250131.aMZWaAoR%fengguang.wu@intel.com> Content-Language: en-US Content-ID: <505169A70A54584083FC35510ADAE221@internal.synopsys.com> Sender: linux-kernel-owner@vger.kernel.org To: "lkp@intel.com" Cc: "kbuild-all@01.org" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "CARLOS.PALMINHA@synopsys.com" , "daniel@ffwll.ch" , "airlied@linux.ie" , "linux-snps-arc@lists.infradead.org" List-Id: dri-devel@lists.freedesktop.org Hello, On Fri, 2016-03-25 at 01:37 +-0800, kbuild test robot wrote: +AD4- Hi Carlos, +AD4- +AD4- +AFs-auto build test ERROR on drm/drm-next+AF0- +AD4- +AFs-also build test ERROR on v4.5 next-20160324+AF0- +AD4- +AFs-if your patch is applied to the wrong git tree, please drop us a note to help improving the system+AF0- +AD4- +AD4- url:+AKAAoACgAKA-https://github.com/0day-ci/linux/commits/Alexey-Brodkin/drm-Add-support-of-ARC-PGU-display-controller/20160325 +AD4- -005345 +AD4- base:+AKAAoACg-git://people.freedesktop.org/+AH4-airlied/linux.git drm-next +AD4- config: i386-allmodconfig (attached as .config) +AD4- reproduce: +AD4- +AKAAoACgAKAAoACgAKAAoAAj- save the attached .config to linux build tree +AD4- +AKAAoACgAKAAoACgAKAAoA-make ARCH+AD0-i386+AKA- +AD4- +AD4- All errors (new ones prefixed by +AD4APg-): +AD4- +AKA- +AKA-230 goto err+AF8-unload+ADs- +AD4- +AKAAoACg-231 +AD4- +AKAAPg- 232 ret +AD0- drm+AF8-connector+AF8-register+AF8-all(drm)+ADs- ... +AD4- +AKAAPg- 254 drm+AF8-connector+AF8-unregister+AF8-all(drm)+ADs- +AD4- +AKAAoACg-255 drm+AF8-dev+AF8-unregister(drm)+ADs- That problem happens because that change relies on another series that yet to be accepted in DRM for 4.7 cycle, see+AKA-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