Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: [linux-next:master 6430/6768] drivers/watchdog/da9052_wdt.c:176:14: error: no member named 'fault_log' in 'struct da9052'
Date: Wed, 8 Jan 2025 14:12:18 +0800	[thread overview]
Message-ID: <202501081401.S714JKUr-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   7b4b9bf203da94fbeac75ed3116c84aa03e74578
commit: 651b5fde35d67a2f669d2c0f5e1b702cac3400b2 [6430/6768] watchdog: da9052_wdt: add support for bootstatus bits
config: i386-randconfig-016-20250108 (https://download.01.org/0day-ci/archive/20250108/202501081401.S714JKUr-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250108/202501081401.S714JKUr-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/202501081401.S714JKUr-lkp@intel.com/

Note: the linux-next/master HEAD 7b4b9bf203da94fbeac75ed3116c84aa03e74578 builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

>> drivers/watchdog/da9052_wdt.c:176:14: error: no member named 'fault_log' in 'struct da9052'
     176 |         if (da9052->fault_log & DA9052_FAULTLOG_TWDERROR)
         |             ~~~~~~  ^
   drivers/watchdog/da9052_wdt.c:178:14: error: no member named 'fault_log' in 'struct da9052'
     178 |         if (da9052->fault_log & DA9052_FAULTLOG_TEMPOVER)
         |             ~~~~~~  ^
   drivers/watchdog/da9052_wdt.c:180:14: error: no member named 'fault_log' in 'struct da9052'
     180 |         if (da9052->fault_log & DA9052_FAULTLOG_VDDFAULT)
         |             ~~~~~~  ^
   3 errors generated.


vim +176 drivers/watchdog/da9052_wdt.c

   153	
   154	
   155	static int da9052_wdt_probe(struct platform_device *pdev)
   156	{
   157		struct device *dev = &pdev->dev;
   158		struct da9052 *da9052 = dev_get_drvdata(dev->parent);
   159		struct da9052_wdt_data *driver_data;
   160		struct watchdog_device *da9052_wdt;
   161		int ret;
   162	
   163		driver_data = devm_kzalloc(dev, sizeof(*driver_data), GFP_KERNEL);
   164		if (!driver_data)
   165			return -ENOMEM;
   166		driver_data->da9052 = da9052;
   167	
   168		da9052_wdt = &driver_data->wdt;
   169	
   170		da9052_wdt->timeout = DA9052_DEF_TIMEOUT;
   171		da9052_wdt->info = &da9052_wdt_info;
   172		da9052_wdt->ops = &da9052_wdt_ops;
   173		da9052_wdt->parent = dev;
   174		watchdog_set_drvdata(da9052_wdt, driver_data);
   175	
 > 176		if (da9052->fault_log & DA9052_FAULTLOG_TWDERROR)
   177			da9052_wdt->bootstatus |= WDIOF_CARDRESET;
   178		if (da9052->fault_log & DA9052_FAULTLOG_TEMPOVER)
   179			da9052_wdt->bootstatus |= WDIOF_OVERHEAT;
   180		if (da9052->fault_log & DA9052_FAULTLOG_VDDFAULT)
   181			da9052_wdt->bootstatus |= WDIOF_POWERUNDER;
   182	
   183		ret = da9052_reg_update(da9052, DA9052_CONTROL_D_REG,
   184					DA9052_CONTROLD_TWDSCALE, 0);
   185		if (ret < 0) {
   186			dev_err(dev, "Failed to disable watchdog bits, %d\n", ret);
   187			return ret;
   188		}
   189	
   190		return devm_watchdog_register_device(dev, &driver_data->wdt);
   191	}
   192	

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

                 reply	other threads:[~2025-01-08  6:12 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=202501081401.S714JKUr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux@roeck-us.net \
    --cc=llvm@lists.linux.dev \
    --cc=marcus.folkesson@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=wim@linux-watchdog.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