Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re:
Date: Sat, 26 Sep 2026 11:08:15 +0800	[thread overview]
Message-ID: <202609261019.YS534QjM-lkp@intel.com> (raw)
In-Reply-To: <202609261019.YS534QjM-lkp@intel.com>

Hi Uwe,

kernel test robot noticed the following build errors:



url:    https://github.com/intel-lab-lkp/linux/commits/Uwe-Kleine-K-nig/Add-TAINT_DRIVER_OVERRIDE-for-usage-of-driver_override/20260925-202040
base:   
patch link:    https://lore.kernel.org/r/202609261019.YS534QjM-lkp%40intel.com
config: s390-allnoconfig (https://download.01.org/0day-ci/archive/20260926/202609261019.YS534QjM-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 78ff5215e53a117851dc6e81e793a106f1a79df8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260926/202609261019.YS534QjM-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609261019.YS534QjM-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/base/bus.c:516:19: error: use of undeclared identifier 'drv'; did you mean 'dev'?
     516 |         add_taint_module(drv->owner, TAINT_DRIVER_OVERRIDE, LOCKDEP_STILL_OK);
         |                          ^~~
         |                          dev
   drivers/base/bus.c:510:53: note: 'dev' declared here
     510 | static ssize_t driver_override_store(struct device *dev,
         |                                                     ^
>> drivers/base/bus.c:516:24: error: no member named 'owner' in 'struct device'
     516 |         add_taint_module(drv->owner, TAINT_DRIVER_OVERRIDE, LOCKDEP_STILL_OK);
         |                          ~~~  ^
   2 errors generated.


vim +516 drivers/base/bus.c

   509	
   510	static ssize_t driver_override_store(struct device *dev,
   511					     struct device_attribute *attr,
   512					     const char *buf, size_t count)
   513	{
   514		int ret;
   515	
 > 516		add_taint_module(drv->owner, TAINT_DRIVER_OVERRIDE, LOCKDEP_STILL_OK);
   517		ret = __device_set_driver_override(dev, buf, count);
   518		if (ret)
   519			return ret;
   520	
   521		return count;
   522	}
   523	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

       reply	other threads:[~2026-09-26  3:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26  3:08 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-26  6:02 kernel test robot
2026-09-25  6:24 Re: kernel test robot
2024-11-25 20:13 Re: Robert Harewood

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=202609261019.YS534QjM-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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