All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [jimc:v5 4/8] lib/dynamic_debug.c:849:34: error: passing 'const struct device' to parameter of incompatible type 'const struct device *'; take the address with &
Date: Wed, 22 Dec 2021 21:10:29 +0800	[thread overview]
Message-ID: <202112222149.XWIfVjsr-lkp@intel.com> (raw)

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

tree:   https://github.com/jimc/linux.git v5
head:   7e7f74e32ba5b42d9e31977d4a2fc75480db8565
commit: 279c262ceba0af1d0ac20d82a9bf4e266d9e8d28 [4/8] dyndbg: add trace-events for pr_debug, dev_dbg
config: hexagon-randconfig-r041-20211222 (https://download.01.org/0day-ci/archive/20211222/202112222149.XWIfVjsr-lkp(a)intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project de4e0195ae1c39f1c3b07834b8e32c113f4f20eb)
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/jimc/linux/commit/279c262ceba0af1d0ac20d82a9bf4e266d9e8d28
        git remote add jimc https://github.com/jimc/linux.git
        git fetch --no-tags jimc v5
        git checkout 279c262ceba0af1d0ac20d82a9bf4e266d9e8d28
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash

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 >>):

   lib/dynamic_debug.c:787:15: warning: variable 'flags' set but not used [-Wunused-but-set-variable]
           unsigned int flags;
                        ^
>> lib/dynamic_debug.c:849:34: error: passing 'const struct device' to parameter of incompatible type 'const struct device *'; take the address with &
                   dynamic_dev_printk(descriptor, ibdev->dev, KERN_DEBUG "%s%s: %pV",
                                                  ^~~~~~~~~~
                                                  &
   lib/dynamic_debug.c:709:75: note: passing argument to parameter 'dev' here
   static void dynamic_dev_printk(struct _ddebug *desc, const struct device *dev,
                                                                             ^
   1 warning and 1 error generated.


vim +849 lib/dynamic_debug.c

   824	
   825	void __dynamic_ibdev_dbg(struct _ddebug *descriptor,
   826				 const struct ib_device *ibdev, const char *fmt, ...)
   827	{
   828		struct va_format vaf;
   829		va_list args;
   830		unsigned int flags;
   831	
   832		va_start(args, fmt);
   833	
   834		vaf.fmt = fmt;
   835		vaf.va = &args;
   836		flags = descriptor->flags;
   837	
   838		if (ibdev && ibdev->dev.parent) {
   839			char buf[PREFIX_SIZE] = "";
   840	
   841			dynamic_dev_printk(descriptor, ibdev->dev.parent,
   842					   "%s%s %s %s: %pV",
   843					   dynamic_emit_prefix(descriptor, buf),
   844					   dev_driver_string(ibdev->dev.parent),
   845					   dev_name(ibdev->dev.parent),
   846					   dev_name(&ibdev->dev),
   847					   &vaf);
   848		} else if (ibdev) {
 > 849			dynamic_dev_printk(descriptor, ibdev->dev, KERN_DEBUG "%s%s: %pV",
   850					   dev_name(&ibdev->dev), &vaf);
   851		} else {
   852			dynamic_printk(descriptor, KERN_DEBUG "(NULL ip_device): %pV",
   853				       &vaf);
   854		}
   855	

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

                 reply	other threads:[~2021-12-22 13:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202112222149.XWIfVjsr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.