All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: adriana@arista.com, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.rg
Cc: oe-kbuild-all@lists.linux.dev, ilpo.jarvinnen@linux.intel.com,
	andriy.shevchenko@linux.intel.com, gregkh@linuxfoundation.org,
	jirislaby@kernel.org, john.ogness@linutronix.de,
	Adriana Nicolae <adriana@arista.com>
Subject: Re: [PATCH v2] serial: 8250 dw: clear FIFO before writting LCR
Date: Wed, 20 Aug 2025 14:33:02 +0800	[thread overview]
Message-ID: <202508201459.9CiUfUhb-lkp@intel.com> (raw)
In-Reply-To: <20250819191314.3452283-1-adriana@arista.com>

Hi,

kernel test robot noticed the following build errors:

[auto build test ERROR on tty/tty-testing]
[also build test ERROR on tty/tty-next tty/tty-linus linus/master v6.17-rc2 next-20250819]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/adriana-arista-com/serial-8250-dw-clear-FIFO-before-writting-LCR/20250820-031410
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link:    https://lore.kernel.org/r/20250819191314.3452283-1-adriana%40arista.com
patch subject: [PATCH v2] serial: 8250 dw: clear FIFO before writting LCR
config: i386-randconfig-002-20250820 (https://download.01.org/0day-ci/archive/20250820/202508201459.9CiUfUhb-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250820/202508201459.9CiUfUhb-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/202508201459.9CiUfUhb-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/tty/serial/8250/8250_dw.c: In function 'dw8250_serial_outapb':
>> drivers/tty/serial/8250/8250_dw.c:267:17: error: too few arguments to function 'dw8250_check_lcr'
     267 |                 dw8250_check_lcr(p, value);
         |                 ^~~~~~~~~~~~~~~~
   drivers/tty/serial/8250/8250_dw.c:155:13: note: declared here
     155 | static void dw8250_check_lcr(struct uart_port *p, unsigned int offset, u32 value)
         |             ^~~~~~~~~~~~~~~~
   drivers/tty/serial/8250/8250_dw.c: In function 'dw8250_quirks':
>> drivers/tty/serial/8250/8250_dw.c:571:22: error: 'DW_UART_QUIRK_DWAPB' undeclared (first use in this function); did you mean 'DW_UART_QUIRK_APB'?
     571 |         if (quirks & DW_UART_QUIRK_DWAPB) {
         |                      ^~~~~~~~~~~~~~~~~~~
         |                      DW_UART_QUIRK_APB
   drivers/tty/serial/8250/8250_dw.c:571:22: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/tty/serial/8250/8250_dw.c:574:31: error: assignment to 'void (*)(struct uart_port *, unsigned int,  u32)' {aka 'void (*)(struct uart_port *, unsigned int,  unsigned int)'} from incompatible pointer type 'void (*)(struct uart_port *, int,  int)' [-Werror=incompatible-pointer-types]
     574 |                 p->serial_out = dw8250_serial_outapb;
         |                               ^
   cc1: some warnings being treated as errors


vim +/dw8250_check_lcr +267 drivers/tty/serial/8250/8250_dw.c

   254	
   255	static void dw8250_serial_outapb(struct uart_port *p, int offset, int value)
   256	{
   257	       struct dw8250_data *d = to_dw8250_data(p->private_data);
   258	
   259		if(offset == UART_LCR && !d->uart_16550_compatible)
   260			dw8250_tx_wait_empty_apb(p);
   261	
   262		writel(value, DW8250_REG(p, offset));
   263	
   264		if (offset == UART_LCR && !d->uart_16550_compatible) {
   265			/* Check FIFO is left enabled and LCR was written */
   266			writel(UART_FCR_ENABLE_FIFO, DW8250_REG(p, UART_FCR));
 > 267			dw8250_check_lcr(p, value);
   268		}
   269	}
   270	

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

  parent reply	other threads:[~2025-08-20  6:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19 19:13 [PATCH v2] serial: 8250 dw: clear FIFO before writting LCR adriana
2025-08-20  4:01 ` Jiri Slaby
2025-08-20  4:06   ` Jiri Slaby
2025-08-20  5:59 ` Greg KH
2025-08-20  6:33 ` kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-19 19:06 adriana
2025-08-20  6:00 ` Greg KH
2025-08-20  6:10   ` Greg KH

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=202508201459.9CiUfUhb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adriana@arista.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinnen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.rg \
    --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 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.