From: kernel test robot <lkp@intel.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH next v2 3/4] serial: 8250: Switch to nbcon console
Date: Sat, 14 Sep 2024 04:51:14 +0800 [thread overview]
Message-ID: <202409140437.EP0Ryw3u-lkp@intel.com> (raw)
In-Reply-To: <20240913140538.221708-4-john.ogness@linutronix.de>
Hi John,
kernel test robot noticed the following build warnings:
[auto build test WARNING on b794563ea12fb46d9499da9e30c33d9607e33697]
url: https://github.com/intel-lab-lkp/linux/commits/John-Ogness/serial-8250-Split-out-IER-from-rs485_start_tx/20240913-220810
base: b794563ea12fb46d9499da9e30c33d9607e33697
patch link: https://lore.kernel.org/r/20240913140538.221708-4-john.ogness%40linutronix.de
patch subject: [PATCH next v2 3/4] serial: 8250: Switch to nbcon console
config: arc-randconfig-001-20240914 (https://download.01.org/0day-ci/archive/20240914/202409140437.EP0Ryw3u-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409140437.EP0Ryw3u-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/202409140437.EP0Ryw3u-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/tty/serial/8250/8250_port.c:1904:13: warning: 'modem_status_handler' defined but not used [-Wunused-function]
1904 | static void modem_status_handler(struct irq_work *iwp)
| ^~~~~~~~~~~~~~~~~~~~
vim +/modem_status_handler +1904 drivers/tty/serial/8250/8250_port.c
1898
1899 /*
1900 * irq_work handler to perform modem control. Only triggered via
1901 * write_atomic() callback because it may be in a scheduler or NMI
1902 * context, unable to wake tasks.
1903 */
> 1904 static void modem_status_handler(struct irq_work *iwp)
1905 {
1906 struct uart_8250_port *up = container_of(iwp, struct uart_8250_port, modem_status_work);
1907 struct uart_port *port = &up->port;
1908
1909 uart_port_lock(port);
1910 serial8250_modem_status(up);
1911 uart_port_unlock(port);
1912 }
1913
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-13 20:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 14:05 [PATCH next v2 0/4] convert 8250 to nbcon John Ogness
2024-09-13 14:05 ` [PATCH next v2 1/4] serial: 8250: Split out IER from rs485_start_tx() John Ogness
2024-09-17 14:48 ` Petr Mladek
2024-09-18 15:04 ` John Ogness
2024-09-19 15:01 ` Petr Mladek
2024-09-13 14:05 ` [PATCH next v2 2/4] serial: 8250: Split out IER from rs485_stop_tx() John Ogness
2024-09-14 10:18 ` kernel test robot
2024-09-18 9:53 ` Petr Mladek
2024-09-13 14:05 ` [PATCH next v2 3/4] serial: 8250: Switch to nbcon console John Ogness
2024-09-13 20:51 ` kernel test robot [this message]
2024-09-13 21:19 ` John Ogness
2024-09-18 12:26 ` Petr Mladek
2024-09-18 14:01 ` Andy Shevchenko
2024-09-18 14:35 ` Petr Mladek
2024-09-18 17:03 ` Andy Shevchenko
2024-09-18 15:19 ` John Ogness
2024-09-18 14:47 ` John Ogness
2024-09-13 14:05 ` [PATCH next v2 4/4] serial: 8250: Revert "drop lockdep annotation from serial8250_clear_IER()" John Ogness
2024-09-18 12:52 ` Petr Mladek
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=202409140437.EP0Ryw3u-lkp@intel.com \
--to=lkp@intel.com \
--cc=john.ogness@linutronix.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.