From: kernel test robot <lkp@intel.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [frank-w-bpi-r2-4.14:6.5-dango-r4_3 19/19] drivers/thermal/mediatek/lvts_thermal.c:1198:13: warning: unused variable 'irq'
Date: Sat, 2 Sep 2023 01:14:25 +0800 [thread overview]
Message-ID: <202309020114.sVLjReEh-lkp@intel.com> (raw)
tree: https://github.com/frank-w/BPI-R2-4.14 6.5-dango-r4_3
head: cf7ba5ba41f644a2e26648583d3489c3f75245d0
commit: cf7ba5ba41f644a2e26648583d3489c3f75245d0 [19/19] lvts: disable interrupt in driver
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20230902/202309020114.sVLjReEh-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230902/202309020114.sVLjReEh-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/202309020114.sVLjReEh-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/thermal/mediatek/lvts_thermal.c: In function 'lvts_probe':
>> drivers/thermal/mediatek/lvts_thermal.c:1198:13: warning: unused variable 'irq' [-Wunused-variable]
1198 | int irq, ret;
| ^~~
drivers/thermal/mediatek/lvts_thermal.c: At top level:
>> drivers/thermal/mediatek/lvts_thermal.c:514:20: warning: 'lvts_irq_handler' defined but not used [-Wunused-function]
514 | static irqreturn_t lvts_irq_handler(int irq, void *data)
| ^~~~~~~~~~~~~~~~
vim +/irq +1198 drivers/thermal/mediatek/lvts_thermal.c
f5f633b18234ce Balsam CHIHI 2023-02-09 1191
f5f633b18234ce Balsam CHIHI 2023-02-09 1192 static int lvts_probe(struct platform_device *pdev)
f5f633b18234ce Balsam CHIHI 2023-02-09 1193 {
f5f633b18234ce Balsam CHIHI 2023-02-09 1194 const struct lvts_data *lvts_data;
f5f633b18234ce Balsam CHIHI 2023-02-09 1195 struct lvts_domain *lvts_td;
f5f633b18234ce Balsam CHIHI 2023-02-09 1196 struct device *dev = &pdev->dev;
f5f633b18234ce Balsam CHIHI 2023-02-09 1197 struct resource *res;
f5f633b18234ce Balsam CHIHI 2023-02-09 @1198 int irq, ret;
f5f633b18234ce Balsam CHIHI 2023-02-09 1199
:::::: The code at line 1198 was first introduced by commit
:::::: f5f633b18234cecb0e6ee6e5fbb358807dda15c3 thermal/drivers/mediatek: Add the Low Voltage Thermal Sensor driver
:::::: TO: Balsam CHIHI <bchihi@baylibre.com>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-01 17:15 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=202309020114.sVLjReEh-lkp@intel.com \
--to=lkp@intel.com \
--cc=frank-w@public-files.de \
--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.