linux-kernel - Re: [PATCH v7] Introduce Cray ClusterStor E1000 NVMe slot LED driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <202512100217.dWKoNRzG-lkp@intel.com>
Date: Wed, 10 Dec 2025 02:57:35 +0800
From: kernel test robot <lkp@...el.com>
To: Tony Hutter <hutter2@...l.gov>, Lukas Wunner <lukas@...ner.de>,
	Bjorn Helgaas <helgaas@...nel.org>
Cc: oe-kbuild-all@...ts.linux.dev, corey@...yard.net,
	alok.a.tiwari@...cle.com, mariusz.tkaczyk@...ux.intel.com,
	minyard@....org, linux-pci@...r.kernel.org,
	openipmi-developer@...ts.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7] Introduce Cray ClusterStor E1000 NVMe slot LED driver

Hi Tony,

kernel test robot noticed the following build warnings:

[auto build test WARNING on pci/next]
[also build test WARNING on pci/for-linus linus/master v6.18 next-20251209]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Tony-Hutter/Introduce-Cray-ClusterStor-E1000-NVMe-slot-LED-driver/20251209-094846
base:   https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link:    https://lore.kernel.org/r/d422a22c-a6fe-4543-ae16-67d64260e0cf%40llnl.gov
patch subject: [PATCH v7] Introduce Cray ClusterStor E1000 NVMe slot LED driver
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20251210/202512100217.dWKoNRzG-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251210/202512100217.dWKoNRzG-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512100217.dWKoNRzG-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/pci/hotplug/pciehp_craye1k.c: In function 'craye1k_get_attention_status':
>> drivers/pci/hotplug/pciehp_craye1k.c:570:25: warning: variable 'craye1k' set but not used [-Wunused-but-set-variable]
     570 |         struct craye1k *craye1k;
         |                         ^~~~~~~


vim +/craye1k +570 drivers/pci/hotplug/pciehp_craye1k.c

   565	
   566	int craye1k_get_attention_status(struct hotplug_slot *hotplug_slot,
   567					 u8 *status)
   568	{
   569		int rc;
 > 570		struct craye1k *craye1k;
   571	
   572		if (mutex_lock_interruptible(&craye1k_lock) != 0)
   573			return -EINTR;
   574	
   575		if (!craye1k_global) {
   576			/* Driver isn't initialized yet */
   577			mutex_unlock(&craye1k_lock);
   578			return -EOPNOTSUPP;
   579		}
   580	
   581		craye1k = craye1k_global;
   582	
   583		rc =  __craye1k_get_attention_status(hotplug_slot, status, true);
   584	
   585		mutex_unlock(&craye1k_lock);
   586		return rc;
   587	}
   588	

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