From: kernel test robot <lkp@intel.com>
To: Hugo Villeneuve <hvilleneuve@dimonoff.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-serial@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: [tty:tty-next 28/31] drivers/tty/serial/max310x.c:1730:1: warning: unused label 'err_spi_register'
Date: Fri, 15 May 2026 07:35:15 +0800 [thread overview]
Message-ID: <202605150707.I4LYaT6N-lkp@intel.com> (raw)
Hi Hugo,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-next
head: 16e95bfb79b5d9d01dc7651d98caf3c2ace331cd
commit: 20ffe4b3330a8bde9e933e9ba2323d5e9386caa5 [28/31] serial: max310x: allow driver to be built with SPI or I2C
config: i386-randconfig-r121-20260515 (https://download.01.org/0day-ci/archive/20260515/202605150707.I4LYaT6N-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260515/202605150707.I4LYaT6N-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/202605150707.I4LYaT6N-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/tty/serial/max310x.c:1730:1: warning: unused label 'err_spi_register' [-Wunused-label]
1730 | err_spi_register:
| ^~~~~~~~~~~~~~~~~
drivers/tty/serial/max310x.c:1280:12: warning: unused function 'max310x_probe' [-Wunused-function]
1280 | static int max310x_probe(struct device *dev, const struct max310x_devtype *devtype,
| ^~~~~~~~~~~~~
drivers/tty/serial/max310x.c:1464:13: warning: unused function 'max310x_remove' [-Wunused-function]
1464 | static void max310x_remove(struct device *dev)
| ^~~~~~~~~~~~~~
>> drivers/tty/serial/max310x.c:1492:29: warning: unused variable 'regcfg' [-Wunused-variable]
1492 | static struct regmap_config regcfg = {
| ^~~~~~
drivers/tty/serial/max310x.c:1507:20: warning: unused function 'max310x_regmap_name' [-Wunused-function]
1507 | static const char *max310x_regmap_name(u8 port_id)
| ^~~~~~~~~~~~~~~~~~~
5 warnings generated.
vim +/err_spi_register +1730 drivers/tty/serial/max310x.c
2e1f2d9a9bdbe12 Cosmin Tanislav 2022-06-05 1729
2e1f2d9a9bdbe12 Cosmin Tanislav 2022-06-05 @1730 err_spi_register:
2e1f2d9a9bdbe12 Cosmin Tanislav 2022-06-05 1731 uart_unregister_driver(&max310x_uart);
2e1f2d9a9bdbe12 Cosmin Tanislav 2022-06-05 1732
51f689cc1133394 Kangjie Lu 2018-12-25 1733 return ret;
6286767ad3afc88 Alexander Shiyan 2016-06-07 1734 }
6286767ad3afc88 Alexander Shiyan 2016-06-07 1735 module_init(max310x_uart_init);
6286767ad3afc88 Alexander Shiyan 2016-06-07 1736
:::::: The code at line 1730 was first introduced by commit
:::::: 2e1f2d9a9bdbe12ee475c82a45ac46a278e8049a serial: max310x: implement I2C support
:::::: TO: Cosmin Tanislav <cosmin.tanislav@analog.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-14 23:51 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=202605150707.I4LYaT6N-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hvilleneuve@dimonoff.com \
--cc=linux-serial@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox