public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Aman Jain <ahjain2706@gmail.com>,
	alexander.deucher@amd.com, christian.koenig@amd.com,
	airlied@linux.ie, daniel@ffwll.ch, amd-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH] This patch replaces all the instances of dev_info with drm_info macro
Date: Tue, 22 Jun 2021 19:22:17 +0800	[thread overview]
Message-ID: <202106221935.wQexectY-lkp@intel.com> (raw)
In-Reply-To: <YNF+Cr9wHupnt3Za@reb0rn>

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

Hi Aman,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.13-rc7 next-20210621]
[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
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Aman-Jain/This-patch-replaces-all-the-instances-of-dev_info-with-drm_info-macro/20210622-140850
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git a96bfed64c8986d6404e553f18203cae1f5ac7e6
config: ia64-randconfig-r005-20210622 (attached as .config)
compiler: ia64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/aa0d692308d703f641f19def814f7c8d59468671
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Aman-Jain/This-patch-replaces-all-the-instances-of-dev_info-with-drm_info-macro/20210622-140850
        git checkout aa0d692308d703f641f19def814f7c8d59468671
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=ia64 

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

All errors (new ones prefixed by >>):

   In file included from include/linux/device.h:15,
                    from include/linux/pm_runtime.h:11,
                    from drivers/gpu/drm/radeon/radeon_drv.c:36:
   drivers/gpu/drm/radeon/radeon_drv.c: In function 'radeon_pci_probe':
>> include/drm/drm_print.h:412:27: error: 'struct device' has no member named 'dev'; did you mean 'devt'?
     412 |  dev_##level##type((drm)->dev, "[drm] " fmt, ##__VA_ARGS__)
         |                           ^~~
   include/linux/dev_printk.h:118:12: note: in definition of macro 'dev_info'
     118 |  _dev_info(dev, dev_fmt(fmt), ##__VA_ARGS__)
         |            ^~~
   include/drm/drm_print.h:416:2: note: in expansion of macro '__drm_printk'
     416 |  __drm_printk((drm), info,, fmt, ##__VA_ARGS__)
         |  ^~~~~~~~~~~~
   drivers/gpu/drm/radeon/radeon_drv.c:311:4: note: in expansion of macro 'drm_info'
     311 |    drm_info(&pdev->dev,
         |    ^~~~~~~~
>> include/drm/drm_print.h:412:27: error: 'struct device' has no member named 'dev'; did you mean 'devt'?
     412 |  dev_##level##type((drm)->dev, "[drm] " fmt, ##__VA_ARGS__)
         |                           ^~~
   include/linux/dev_printk.h:118:12: note: in definition of macro 'dev_info'
     118 |  _dev_info(dev, dev_fmt(fmt), ##__VA_ARGS__)
         |            ^~~
   include/drm/drm_print.h:416:2: note: in expansion of macro '__drm_printk'
     416 |  __drm_printk((drm), info,, fmt, ##__VA_ARGS__)
         |  ^~~~~~~~~~~~
   drivers/gpu/drm/radeon/radeon_drv.c:323:4: note: in expansion of macro 'drm_info'
     323 |    drm_info(&pdev->dev,
         |    ^~~~~~~~


vim +412 include/drm/drm_print.h

02c9656b2f0d69 Haneen Mohammed       2017-10-17  378  
02c9656b2f0d69 Haneen Mohammed       2017-10-17  379  /**
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  380   * DRM_DEV_DEBUG() - Debug output for generic drm code
02c9656b2f0d69 Haneen Mohammed       2017-10-17  381   *
091756bbb1a961 Haneen Mohammed       2017-10-17  382   * @dev: device pointer
091756bbb1a961 Haneen Mohammed       2017-10-17  383   * @fmt: printf() like format string.
02c9656b2f0d69 Haneen Mohammed       2017-10-17  384   */
db87086492581c Joe Perches           2018-03-16  385  #define DRM_DEV_DEBUG(dev, fmt, ...)					\
db87086492581c Joe Perches           2018-03-16  386  	drm_dev_dbg(dev, DRM_UT_CORE, fmt, ##__VA_ARGS__)
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  387  /**
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  388   * DRM_DEV_DEBUG_DRIVER() - Debug output for vendor specific part of the driver
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  389   *
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  390   * @dev: device pointer
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  391   * @fmt: printf() like format string.
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  392   */
db87086492581c Joe Perches           2018-03-16  393  #define DRM_DEV_DEBUG_DRIVER(dev, fmt, ...)				\
db87086492581c Joe Perches           2018-03-16  394  	drm_dev_dbg(dev, DRM_UT_DRIVER,	fmt, ##__VA_ARGS__)
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  395  /**
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  396   * DRM_DEV_DEBUG_KMS() - Debug output for modesetting code
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  397   *
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  398   * @dev: device pointer
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  399   * @fmt: printf() like format string.
b52817e9de06a3 Mauro Carvalho Chehab 2020-10-27  400   */
db87086492581c Joe Perches           2018-03-16  401  #define DRM_DEV_DEBUG_KMS(dev, fmt, ...)				\
db87086492581c Joe Perches           2018-03-16  402  	drm_dev_dbg(dev, DRM_UT_KMS, fmt, ##__VA_ARGS__)
a18b21929453af Lyude Paul            2018-07-16  403  
fb6c7ab8718eb2 Jani Nikula           2019-12-10  404  /*
fb6c7ab8718eb2 Jani Nikula           2019-12-10  405   * struct drm_device based logging
fb6c7ab8718eb2 Jani Nikula           2019-12-10  406   *
fb6c7ab8718eb2 Jani Nikula           2019-12-10  407   * Prefer drm_device based logging over device or prink based logging.
fb6c7ab8718eb2 Jani Nikula           2019-12-10  408   */
fb6c7ab8718eb2 Jani Nikula           2019-12-10  409  
fb6c7ab8718eb2 Jani Nikula           2019-12-10  410  /* Helper for struct drm_device based logging. */
fb6c7ab8718eb2 Jani Nikula           2019-12-10  411  #define __drm_printk(drm, level, type, fmt, ...)			\
fb6c7ab8718eb2 Jani Nikula           2019-12-10 @412  	dev_##level##type((drm)->dev, "[drm] " fmt, ##__VA_ARGS__)
fb6c7ab8718eb2 Jani Nikula           2019-12-10  413  
fb6c7ab8718eb2 Jani Nikula           2019-12-10  414  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

  parent reply	other threads:[~2021-06-22 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  6:07 [PATCH] This patch replaces all the instances of dev_info with drm_info macro Aman Jain
2021-06-22  6:40 ` Christian König
2021-06-22 11:22 ` kernel test robot [this message]
2021-06-22 11:47 ` kernel test robot

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=202106221935.wQexectY-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ahjain2706@gmail.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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