All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 2/2] drivers/hid/hid-steam.c:1154:7: warning: variable 'connected' set but not used
Date: Sat, 13 Dec 2025 16:29:14 +0800	[thread overview]
Message-ID: <202512131626.ScDIN2jG-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android15-6.6
head:   5580efd2c7e4791254a0c26f9791aaa33dd70484
commit: e1147961b2145fa61c3078a4a797d9576cde91ab [2/2] HID: hid-steam: Move hidraw input (un)registering to work
config: i386-buildonly-randconfig-005-20251213 (https://download.01.org/0day-ci/archive/20251213/202512131626.ScDIN2jG-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512131626.ScDIN2jG-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/202512131626.ScDIN2jG-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/hid/hid-steam.c:1154:7: warning: variable 'connected' set but not used [-Wunused-but-set-variable]
    1154 |         bool connected;
         |              ^
   1 warning generated.


vim +/connected +1154 drivers/hid/hid-steam.c

c164d6abf3841f Rodrigo Rivas Costa 2018-04-16  1148  
c164d6abf3841f Rodrigo Rivas Costa 2018-04-16  1149  static void steam_client_ll_close(struct hid_device *hdev)
c164d6abf3841f Rodrigo Rivas Costa 2018-04-16  1150  {
4bff980f920693 Rodrigo Rivas Costa 2018-05-22  1151  	struct steam_device *steam = hdev->driver_data;
c164d6abf3841f Rodrigo Rivas Costa 2018-04-16  1152  
6b538cc21334b8 Rodrigo Rivas Costa 2019-03-15  1153  	unsigned long flags;
6b538cc21334b8 Rodrigo Rivas Costa 2019-03-15 @1154  	bool connected;
6b538cc21334b8 Rodrigo Rivas Costa 2019-03-15  1155  
6b538cc21334b8 Rodrigo Rivas Costa 2019-03-15  1156  	spin_lock_irqsave(&steam->lock, flags);
9544708c64bc2c Vicki Pfau          2023-12-19  1157  	steam->client_opened = false;
9544708c64bc2c Vicki Pfau          2023-12-19  1158  	connected = steam->connected && !steam->client_opened;
6b538cc21334b8 Rodrigo Rivas Costa 2019-03-15  1159  	spin_unlock_irqrestore(&steam->lock, flags);
6b538cc21334b8 Rodrigo Rivas Costa 2019-03-15  1160  
e1147961b2145f Vicki Pfau          2025-02-04  1161  	schedule_work(&steam->unregister_work);
9544708c64bc2c Vicki Pfau          2023-12-19  1162  }
c164d6abf3841f Rodrigo Rivas Costa 2018-04-16  1163  

:::::: The code at line 1154 was first introduced by commit
:::::: 6b538cc21334b83f09b25dec4aa2d2726bf07ed0 HID: steam: fix deadlock with input devices.

:::::: TO: Rodrigo Rivas Costa <rodrigorivascosta@gmail.com>
:::::: CC: Jiri Kosina <jkosina@suse.cz>

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

                 reply	other threads:[~2025-12-13  8:29 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=202512131626.ScDIN2jG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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 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.