From: kernel test robot <lkp@intel.com>
To: Tony Hutter <hutter2@llnl.gov>, Lukas Wunner <lukas@wunner.de>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, corey@minyard.net,
alok.a.tiwari@oracle.com, mariusz.tkaczyk@linux.intel.com,
minyard@acm.org, linux-pci@vger.kernel.org,
openipmi-developer@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7] Introduce Cray ClusterStor E1000 NVMe slot LED driver
Date: Wed, 10 Dec 2025 02:57:35 +0800 [thread overview]
Message-ID: <202512100217.dWKoNRzG-lkp@intel.com> (raw)
In-Reply-To: <d422a22c-a6fe-4543-ae16-67d64260e0cf@llnl.gov>
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@intel.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
prev parent reply other threads:[~2025-12-09 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 1:05 Tony Hutter
2025-12-09 18:57 ` kernel test robot [this message]
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=202512100217.dWKoNRzG-lkp@intel.com \
--to=lkp@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=corey@minyard.net \
--cc=helgaas@kernel.org \
--cc=hutter2@llnl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=minyard@acm.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=openipmi-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®