Hi Fengguang, On 07/24/2015 12:26 PM, kbuild test robot wrote: > tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing > head: d684779335856d8177514b42a801d46088d897b0 > commit: b6830f6df8914faae9561bb245860c21af9b9e9b [23/50] serial: 8250: Split base port operations from universal driver > config: m32r-usrv_defconfig (attached as .config) > reproduce: > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > git checkout b6830f6df8914faae9561bb245860c21af9b9e9b > # save the attached .config to linux build tree > make.cross ARCH=m32r > > All error/warnings (new ones prefixed by >>): > > drivers/tty/serial/8250/8250_port.c: In function 'mem32be_serial_out': >>> drivers/tty/serial/8250/8250_port.c:378:2: error: implicit declaration of function 'iowrite32be' [-Werror=implicit-function-declaration] > iowrite32be(value, p->membase + offset); > ^ > drivers/tty/serial/8250/8250_port.c: In function 'mem32be_serial_in': >>> drivers/tty/serial/8250/8250_port.c:384:2: error: implicit declaration of function 'ioread32be' [-Werror=implicit-function-declaration] > return ioread32be(p->membase + offset); > ^ > cc1: some warnings being treated as errors These build errors should be fixed by commit 7525a9901b5e ("m32r: Add ioreadXX/iowriteXX big-endian mmio accessors") Regards, Peter Hurley > vim +/iowrite32be +378 drivers/tty/serial/8250/8250_port.c > > 372 return readl(p->membase + offset); > 373 } > 374 > 375 static void mem32be_serial_out(struct uart_port *p, int offset, int value) > 376 { > 377 offset = offset << p->regshift; > > 378 iowrite32be(value, p->membase + offset); > 379 } > 380 > 381 static unsigned int mem32be_serial_in(struct uart_port *p, int offset) > 382 { > 383 offset = offset << p->regshift; > > 384 return ioread32be(p->membase + offset); > 385 } > 386 > 387 static unsigned int io_serial_in(struct uart_port *p, int offset) -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
