From: kbuild test robot <lkp@intel.com>
Cc: linux-arch@vger.kernel.org, alexandre.belloni@bootlin.com,
arnd@arndb.de, richard.genoud@gmail.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Ludovic Desroches <ludovic.desroches@microchip.com>,
kbuild-all@01.org, linux-serial@vger.kernel.org, jslaby@suse.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] tty/serial_core: add ISO7816 infrastructure
Date: Fri, 20 Jul 2018 07:54:50 +0800 [thread overview]
Message-ID: <201807200737.cwPwFKNL%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180719084737.1490-2-ludovic.desroches@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 4392 bytes --]
Hi Nicolas,
I love your patch! Yet something to improve:
[auto build test ERROR on tty/tty-testing]
[also build test ERROR on v4.18-rc5 next-20180719]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Ludovic-Desroches/tty-serial_core-add-ISO7816-infrastructure/20180719-183102
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
config: parisc-generic-64bit_defconfig (attached as .config)
compiler: hppa64-linux-gnu-gcc (GCC) 7.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.3.0 make.cross ARCH=parisc
All errors (new ones prefixed by >>):
drivers/tty/serial/serial_core.c: In function 'uart_ioctl':
>> drivers/tty/serial/serial_core.c:1448:7: error: 'TIOCSISO7816' undeclared (first use in this function); did you mean 'TIOCSRS485'?
case TIOCSISO7816:
^~~~~~~~~~~~
TIOCSRS485
drivers/tty/serial/serial_core.c:1448:7: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/tty/serial/serial_core.c:1452:7: error: 'TIOCGISO7816' undeclared (first use in this function); did you mean 'TIOCSISO7816'?
case TIOCGISO7816:
^~~~~~~~~~~~
TIOCSISO7816
vim +1448 drivers/tty/serial/serial_core.c
1362
1363 /*
1364 * Called via sys_ioctl. We can use spin_lock_irq() here.
1365 */
1366 static int
1367 uart_ioctl(struct tty_struct *tty, unsigned int cmd, unsigned long arg)
1368 {
1369 struct uart_state *state = tty->driver_data;
1370 struct tty_port *port = &state->port;
1371 struct uart_port *uport;
1372 void __user *uarg = (void __user *)arg;
1373 int ret = -ENOIOCTLCMD;
1374
1375
1376 /*
1377 * These ioctls don't rely on the hardware to be present.
1378 */
1379 switch (cmd) {
1380 case TIOCGSERIAL:
1381 ret = uart_get_info_user(port, uarg);
1382 break;
1383
1384 case TIOCSSERIAL:
1385 down_write(&tty->termios_rwsem);
1386 ret = uart_set_info_user(tty, state, uarg);
1387 up_write(&tty->termios_rwsem);
1388 break;
1389
1390 case TIOCSERCONFIG:
1391 down_write(&tty->termios_rwsem);
1392 ret = uart_do_autoconfig(tty, state);
1393 up_write(&tty->termios_rwsem);
1394 break;
1395
1396 case TIOCSERGWILD: /* obsolete */
1397 case TIOCSERSWILD: /* obsolete */
1398 ret = 0;
1399 break;
1400 }
1401
1402 if (ret != -ENOIOCTLCMD)
1403 goto out;
1404
1405 if (tty_io_error(tty)) {
1406 ret = -EIO;
1407 goto out;
1408 }
1409
1410 /*
1411 * The following should only be used when hardware is present.
1412 */
1413 switch (cmd) {
1414 case TIOCMIWAIT:
1415 ret = uart_wait_modem_status(state, arg);
1416 break;
1417 }
1418
1419 if (ret != -ENOIOCTLCMD)
1420 goto out;
1421
1422 mutex_lock(&port->mutex);
1423 uport = uart_port_check(state);
1424
1425 if (!uport || tty_io_error(tty)) {
1426 ret = -EIO;
1427 goto out_up;
1428 }
1429
1430 /*
1431 * All these rely on hardware being present and need to be
1432 * protected against the tty being hung up.
1433 */
1434
1435 switch (cmd) {
1436 case TIOCSERGETLSR: /* Get line status register */
1437 ret = uart_get_lsr_info(tty, state, uarg);
1438 break;
1439
1440 case TIOCGRS485:
1441 ret = uart_get_rs485_config(uport, uarg);
1442 break;
1443
1444 case TIOCSRS485:
1445 ret = uart_set_rs485_config(uport, uarg);
1446 break;
1447
> 1448 case TIOCSISO7816:
1449 ret = uart_set_iso7816_config(state->uart_port, uarg);
1450 break;
1451
> 1452 case TIOCGISO7816:
1453 ret = uart_get_iso7816_config(state->uart_port, uarg);
1454 break;
1455 default:
1456 if (uport->ops->ioctl)
1457 ret = uport->ops->ioctl(uport, cmd, arg);
1458 break;
1459 }
1460 out_up:
1461 mutex_unlock(&port->mutex);
1462 out:
1463 return ret;
1464 }
1465
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 19052 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-07-19 23:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 8:47 [PATCH v2 0/2] add ISO7816 support Ludovic Desroches
2018-07-19 8:47 ` Ludovic Desroches
2018-07-19 8:47 ` [PATCH v2 1/2] tty/serial_core: add ISO7816 infrastructure Ludovic Desroches
2018-07-19 8:47 ` Ludovic Desroches
2018-07-19 23:54 ` kbuild test robot [this message]
2018-07-19 8:47 ` [PATCH v2 2/2] tty/serial: atmel: add ISO7816 support Ludovic Desroches
2018-07-19 8:47 ` Ludovic Desroches
2018-07-27 14:39 ` Richard Genoud
2018-07-27 14:39 ` Richard Genoud
2018-08-03 8:50 ` Ludovic Desroches
2018-08-03 8:50 ` Ludovic Desroches
2018-07-19 8:59 ` [PATCH v2 0/2] " Neil Armstrong
2018-07-19 8:59 ` Neil Armstrong
2018-07-19 9:26 ` Ludovic Desroches
2018-07-19 9:26 ` Ludovic Desroches
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=201807200737.cwPwFKNL%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=richard.genoud@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).