All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jirislaby:devel 53/90] drivers/tty/serial/serial_core.c:1087:6: warning: unused variable 'result'
Date: Tue, 10 Jun 2025 10:49:55 +0800	[thread overview]
Message-ID: <202506101035.cEBHA2Ng-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head:   ddc23bf3036b252a58a07fbcf74b3a0a6cb3582d
commit: 555da4e8dcbc70496db3e4cf4c9e15ab0e1a2bd2 [53/90] serial_core: use GUARDs
config: arm-randconfig-002-20250610 (https://download.01.org/0day-ci/archive/20250610/202506101035.cEBHA2Ng-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250610/202506101035.cEBHA2Ng-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/202506101035.cEBHA2Ng-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/tty/serial/serial_core.c: In function 'uart_tiocmget':
>> drivers/tty/serial/serial_core.c:1087:6: warning: unused variable 'result' [-Wunused-variable]
     int result;
         ^~~~~~


vim +/result +1087 drivers/tty/serial/serial_core.c

^1da177e4c3f41 drivers/serial/serial_core.c     Linus Torvalds    2005-04-16  1081  
60b33c133ca0b7 drivers/tty/serial/serial_core.c Alan Cox          2011-02-14  1082  static int uart_tiocmget(struct tty_struct *tty)
^1da177e4c3f41 drivers/serial/serial_core.c     Linus Torvalds    2005-04-16  1083  {
^1da177e4c3f41 drivers/serial/serial_core.c     Linus Torvalds    2005-04-16  1084  	struct uart_state *state = tty->driver_data;
a2bceae065ed8c drivers/serial/serial_core.c     Alan Cox          2009-09-19  1085  	struct tty_port *port = &state->port;
4047b37122d1be drivers/tty/serial/serial_core.c Peter Hurley      2016-04-09  1086  	struct uart_port *uport;
5879adbff5aad0 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2024-08-08 @1087) 	int result;
5879adbff5aad0 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2024-08-08  1088) 
5879adbff5aad0 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2024-08-08  1089) 	guard(mutex)(&port->mutex);
^1da177e4c3f41 drivers/serial/serial_core.c     Linus Torvalds    2005-04-16  1090  
4047b37122d1be drivers/tty/serial/serial_core.c Peter Hurley      2016-04-09  1091  	uport = uart_port_check(state);
5879adbff5aad0 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2024-08-08  1092) 	if (!uport || tty_io_error(tty))
5879adbff5aad0 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2024-08-08  1093) 		return -EIO;
4047b37122d1be drivers/tty/serial/serial_core.c Peter Hurley      2016-04-09  1094  
555da4e8dcbc70 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2025-04-15  1095) 	guard(uart_port_lock_irq)(uport);
5879adbff5aad0 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2024-08-08  1096) 
555da4e8dcbc70 drivers/tty/serial/serial_core.c Jiri Slaby (SUSE  2025-04-15  1097) 	return uport->mctrl | uport->ops->get_mctrl(uport);
^1da177e4c3f41 drivers/serial/serial_core.c     Linus Torvalds    2005-04-16  1098  }
^1da177e4c3f41 drivers/serial/serial_core.c     Linus Torvalds    2005-04-16  1099  

:::::: The code at line 1087 was first introduced by commit
:::::: 5879adbff5aad0436298db006a922dd576339c7f serial: use guards for simple mutex locks

:::::: TO: Jiri Slaby (SUSE) <jirislaby@kernel.org>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

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

                 reply	other threads:[~2025-06-10  2:50 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=202506101035.cEBHA2Ng-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jirislaby@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 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.