archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <>
To: Arnd Bergmann <>, Rob Clark <>,
	Sean Paul <>, David Airlie <>,
	Daniel Vetter <>,
	Sharat Masetty <>,
	Sai Prakash Ranjan <>
Cc:, Arnd Bergmann <>,,,
	Tanmay Shah <>
Subject: Re: [PATCH] drm/msm/a6xx: add CONFIG_QCOM_LLCC dependency
Date: Mon, 4 Jan 2021 00:21:35 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Hi Arnd,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.11-rc1 next-20201223]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in]

base: 3516bd729358a2a9b090c1905bd2a3fa926e24c6
config: x86_64-rhel (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
        git remote add linux-review
        git fetch --no-tags linux-review Arnd-Bergmann/drm-msm-a6xx-add-CONFIG_QCOM_LLCC-dependency/20210103-220704
        git checkout 7d8b8d7954012e210a5e6c77103e52382c6b5503
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <>

All errors (new ones prefixed by >>):

>> Error: kernelrelease not valid - run 'make prepare' to update it
>> drivers/gpu/drm/Kconfig:74:error: recursive dependency detected!
   drivers/gpu/drm/Kconfig:74: symbol DRM_KMS_HELPER is selected by DRM_MSM
   drivers/gpu/drm/msm/Kconfig:3: symbol DRM_MSM depends on QCOM_COMMAND_DB
   drivers/soc/qcom/Kconfig:19: symbol QCOM_COMMAND_DB depends on OF_RESERVED_MEM
   drivers/of/Kconfig:80: symbol OF_RESERVED_MEM default is visible depending on DMA_CMA
   kernel/dma/Kconfig:109: symbol DMA_CMA is selected by FB_HYPERV
   drivers/video/fbdev/Kconfig:2182: symbol FB_HYPERV depends on FB
   drivers/video/fbdev/Kconfig:12: symbol FB is selected by DRM_KMS_FB_HELPER
   drivers/gpu/drm/Kconfig:80: symbol DRM_KMS_FB_HELPER depends on DRM_KMS_HELPER
   For a resolution refer to Documentation/kbuild/kconfig-language.rst
   subsection "Kconfig recursive dependency limitations"
   Makefile arch drivers include scripts source usr [scripts/kconfig/Makefile:71: syncconfig] Error 1
   Makefile arch drivers include scripts source usr [Makefile:602: syncconfig] Error 2
   Makefile arch drivers include scripts source usr [Makefile:710: include/config/auto.conf.cmd] Error 2
   Failed to remake makefile 'include/config/auto.conf.cmd'.
   Failed to remake makefile 'include/config/auto.conf'.
   Makefile arch drivers include scripts source usr [arch/x86/Makefile:278: checkbin] Error 1
>> Error: kernelrelease not valid - run 'make prepare' to update it
   Target 'prepare' not remade because of errors.
   make: Makefile arch drivers include scripts source usr [Makefile:185: __sub-make] Error 2
   make: Target 'prepare' not remade because of errors.

0-DAY CI Kernel Test Service, Intel Corporation

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

      parent reply	other threads:[~2021-01-03 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 14:03 [PATCH] drm/msm/a6xx: add CONFIG_QCOM_LLCC dependency Arnd Bergmann
2021-01-03 15:09 ` kernel test robot
2021-01-03 15:24   ` Arnd Bergmann
2021-01-04  7:23     ` Sai Prakash Ranjan
2021-01-03 16:21 ` kernel 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).